Depending on your company’s needs, choose the localization levels to translate at. Below are several possible scenarios.
These scenarios illustrate the general configuration logic and do not replace detailed instructions. For each step, you will find links to articles describing the required actions in detail.
Scenario 1: Full transition to a new locale
All employees in your company use a language that is not supported by default, such as French. You plan to use only this language in your work.
In this case:
- Install a new locale by obtaining the .po resource file from BRIX technical support and translating it into French.
- Translate resources at the configuration level. This allows you to localize all default elements in the system.
- Set the added language as the default interface language in the company settings.
- Develop custom components directly in French. To do this, the administrator needs to select this language in their profile before creating a workspace or a module.
- Maintain translations when updating the system version.
Scenario 2: International team workflow
The company employs staff from different countries. For example, different departments use English, Serbian, and Czech. New components in the system are developed in English.
In this case:
- Install locales for unsupported languages by obtaining the .po resource files from BRIX technical support and translating them.
- For each new language, choose a localization method and translate resources:
- At the configuration level. For example, if the department in Serbia works with the entire system, you need to localize all interfaces. If necessary, you can individually override the translation of specific headers, fields, etc., using the component level.
- At the component level. For example, if employees from the Czech Republic work only in specific workspaces, you do not need to translate the entire system. Part of the interface will be displayed in English for these users.
- Maintain translations when updating the system version or adding new components.
Scenario 3: Translating custom interfaces into a supported language
A company has an branch whose employees use system features in German. New components in the system are developed in English.
Since German is supported by default, there is no need to add a new locale. Follow these steps:
- Compliment the existing configuration translation for German to localize custom components.
- Maintain translations when adding new components to the company.