UI localization

ActivePlatform is delivered including the English and Russian locales. Users can switch between the languages of the interface both in the Operator Control Panel (see Screen layout) and Customer Control Panel (see Screen layout).

Unlike the Operator Control Panel and Customer Control Panel, localization of Storefront does not use the localise.biz service. For information about languages and translations in Customer Store, see Managing Customer Store language.

To add more localizations of the user interface, integration with localise.biz, a translation management system, is implemented. A translator, as a member of the project team at localise.biz, edits translations from the source language to several locales while the platform updates the localizations of the user interface via the API service. The current implementation supports daily automatic synchronization with localise.biz. If for a locale, the translation of an element is missing, the element in the interface is displayed in English.

To add a new localization of the user interface in ActivePlatform:

  1. As a manager, create and configure a new project at localise.biz:
    1. Create a new project and set English as the Source locale. This project will be used for translations to all languages (see Starting a project).
    2. In the project, add new target languages as Locales (see Project locales).
    3. Create the Full access key for API (see API keys).
    4. Provide the ActivePlatform technical support team with the project parameters including the Full access key.
  2. As the ActivePlatform technical support team, update the system configuration file and set up the initial synchronization of the platform with localise.biz.

  3. Wait until ActivePlatform will send to localise.biz YML files of the Source locale for each component of the platform.

    Depending on the current plan at localise.biz, there is a limit to the maximum number of elements (assets) to be translated. When YML files are sent to localise.biz and the limit is reached, the rest part of the elements will not be available in the project. To increase the limit and allow all elements to be translated, it is necessary to upgrade the plan (see Plans and pricing) and send the YML files one more time.

  4. As a translator, edit the required elements of a target locale.

    Expressions like %{...} (for example, %{billing_day} or %{status}), regular expressions, and the names of the HTML tags must not be translated.

  5. As a manager, ensure that ActivePlatform on schedule received the locales updates from localise.biz.