Localization and multilingual translations

In BRIX, you can flexibly configure your company’s language environment for effective collaboration across international teams. You can:

  1. Add any number of languages.

The following languages are available by default:

  • English for SaaS.
  • English, Spanish, and German for On-Premises.

You can add any other languages relevant to your company, as well as supplement existing translations for the default languages by localizing your custom configuration.

The system administrator sets the company’s default interface language, which users see by default. An employee can select a language in their profile settings. All translated interfaces will then display in the selected language, while any untranslated elements will appear in the company's default language.

  1. Translate the entire interface or individual components.

If your employees use all system features in different languages, you can translate the entire system. For international teams that only use specific workspaces, you can translate just the relevant components.

  1. Use translation inheritance.

To simplify the localization process, you can define translations for recurring names once at the configuration level. Interfaces throughout the system will inherit these translations.

If a different translation is needed in a specific location, you can override it at the component level.

  1. Translate from any language.

Translation works in any direction, so components do not need to be created in the system's default language. You can configure a workspace, app, business process, or interface in any language, which is recorded as the source language for the component, and then translate it into other languages as needed.

Localization terminology

The following key concepts are essential for configuring localization:

  • Multilingual support. The ability to use the system in multiple languages by switching between them.
  • Localization. The process of translating and adapting system interfaces so that users can work in a different language.
  • Locale. A language pack that enables the system interface to display in a specific language. To add language support, you install a new locale in the system.
  • Resources. Interface text data that requires translation, such as field names, button labels, workspace titles, notifications, and so on. Resources are stored in .po files, where you add a translation for each line of the original text.

Localization levels and the inheritance principle

Your company’s approach to localization may vary depending on your needs. You can add support for an additional locale, translate custom components into a default language, localize only specific workspaces, and so on.

Based on this, you choose which levels to translate at:

  1. Locale level.
  2. Configuration level.
  3. Component level.

Each level has its own separate .po resource files.

Translation at the locale level

Translation at this level is required to add a language to your company, so it is mandatory for additional locales. For default languages, it is provided with the system.

This level covers the resources of core system components: primary buttons and system notifications, data types, the Tasks workspace, the interface and business process designer, and so on.

Translation at the configuration level

This allows you to localize the entire company configuration, including custom components, in a single .po file. Recurring text fragments are translated only once, and the same translations are applied throughout the system.

If you do not need to localize the entire interface into another language, translation at this level is not required.

The configuration level includes resources for:

  • Standard processes for review and approval, task assignment, and so on.
  • System workspaces: CRM, Revenues, Marketing, Live Chats, Projects, and System Apps.
  • All custom components that you have added to your company.

Translation at the component level

This includes the resources of a specific system or custom workspace or module. Translations defined at this level take precedence over translations at the configuration level.

Adding translations at the component level is optional. You can use it to:

  • Override the translation of specific text fragments within a component.

For example, at the configuration level, the word “Order” is translated into German as “Bestellung”, and this translation is applied across all system interfaces. Using component-level localization, you can individually change the translation in a specific interface. For instance, in the Production Planning app, you can translate the “Order” field as “Auftrag”.

  • Translate the resources of a component that has no translations at the configuration level.

For example, if a team in Portugal only needs one workspace in the system, you can skip the configuration-level translation into Portuguese and localize only that workspace.

Translation inheritance

Thanks to the inheritance principle, translations are applied as follows:

  1. If a translation is defined at the component level, this translation will be shown to the user.
  2. If no component-level translation exists, the configuration-level translation will be displayed.
  3. If no translation exists at either level, the text will be displayed in the company’s default language.

начало примечание

Useful articles:

конец примечание

locale-settings.html localization-use-cases.html