Skip to content

Translations in Configurations

Translations vs Prog Text

The prog text is the text displayed in the configuration designer. This text will also be used at runtime unless a translation exists for the current language setting. For example, if a label is modified in a page using the Page Designer, that label will appear the same to all users, regardless of their selected language. The prog text must be translated into each required language. It is also possible to provide translations for only a subset of languages. If a translation is not available for a specific language, the system will fall back to displaying the prog text.

This means it is possible to reduce translation effort by writing the prog text in one of the required languages and only translating it into the other necessary languages.

Scan Translatable Items

The translation process involves two main steps. The first step is to scan for Translatable Items, also known as Translatable Texts.

Then the found translatable items can be translated into different languages. Client configurations—such as page configurations and connected navigator items—are scanned from the Page Configurations administrative page.

Select the 'Client Model' to scan. Then run 'Scan Translatable Items' from the 'Translations' menu.

Scan translatable items for a selected client model.

Translate

When translatable items are scanned they can be translated. Translation is initiated from the 'Solution Manager' page Translatable Text. In this page you search for the 'Translation Texts' to translate and then execute the 'Add Translations' command.

The simplest way to find the translatable items for your configuration is to navigate from the 'Page Configuration' page. Select the 'Client Model' for which you want to filter 'Translatable Items', then choose 'View Translatable Items' from the 'Translations' menu. This will open the 'Translatable Text' page and filter out the configuration translatable items for the selected client model.

Filter Configuration Translatable Texts

  • Module: Configuration Items are always saved for module CONFIG.

  • Main Type: Client configuration items will have the main type Configuration Client

  • Layer: Configuration items are saved in the User layer.

  • Path: The path for the translatable item contains important components.

  • Configuration Context: The first part of the path enclosed in brackets (e.g., [global]) represents the 'Configuration Context'.

  • Client Model: Follows the context. For example, in configurations for the client model Customer, this part helps in filtering relevant items.

  • Prog Text: You can also search using a specific prog text value.

Note:

If translations are added under multiple contexts, separate translation paths will be created for each. This means each item must be translated individually for every context.

Export Language Files

Use the Export Language Files assistant to export .lng and .trs files for persistence in the customer solution repository.

When exporting Client Configuration translations, use the following settings:

  • Files: Language file, Translation file or All
  • Layer: User
  • Main type: Configuration Client
  • Module: CONFIG.

Import Language Files

Use the 'Import Language Files' assistant to import language files.

Note:

When importing a .lng file, all existing translation contexts in the environment matching the specified layer, main type, and module will be marked as obsolete. Any translatable items not present in the imported file will be removed. This requires that the imported language file fully represents the desired translation state. Language files from multiple sources cannot be merged—only the latest import is retained.

Configuration Translation Process

It is generally recommended to use a separate environment for translation work. However, with a solid understanding of the translation process and tools, it is feasible to manage translations in the same environment used for development. Keep in mind: some configurations automatically generate translatable items upon creation or update. These may unintentionally be included in exported files during ongoing development work.

Life Cycle process:

Managing the translation lifecycle includes backing up your work and updating content as configurations evolve:

  1. Extract .lng and .trs files for client configurations from the customer solution repository.
  2. Import language and translation files into the environment
  3. Scan modified clients and associated navigator items for translatable texts.
  4. Translate new translatable texts into the required languages.
  5. Export updated language files.
  6. Optionally, compare exported files with the originals to verify changes.
  7. Check in the updated files to the customer solution repository.

See the note under 'Import Language Files' for important details.