Languages

This feature offers the option of translating text elements of the user interface yourself or, if necessary, adapting existing translations. So-called language keys are available for this purpose, each consisting of a translation key and a translation.

Translation keys are stored, for example, on buttons and other text-based elements. These are texts that reference a specific entry in the currently loaded language file. Depending on which language has been selected in the BPC (see Select language), different language files are loaded.
There can be exactly one translation per language for each translation key.

The settings made here apply to all users throughout the BPC.

User interface

Area 1: List of all translation keys and translations
Area 2: Language editor
Area 3: Toolbar

Add new translation

By default, a German and an English translation are already stored for all language keys in the BPC.
Any number of additional languages can be added.

Two fields are created in the language editor for each newly created language:

Translation	Contains the value of the stored default translation and cannot be edited.
User-specific translation	Entry field for the desired translation. If something is entered in this field, the selected key BPC wide is replaced with this user-defined translation.

Add new translation

Select the translation key from the list.
Click the "Add language" button.
A window opens.
Select the language code.
Click on "Add".
The new language appears in the editor.
The languages are automatically arranged in alphabetical order of the language code.
Enter the desired text in the "Translation" field of the newly created language.
Save.
Reload the page to see the changes.

Own translation/custom translation

Language keys that have already been "translated", e.g. German or English text elements, can be adapted to the user by manually overwriting the translation keys.
This is possible in the setting Core_CustomTranslations, see Core Services settings.

Thus, for example, buttons with the label "Save" can be given a new label "Save":

Example for overwriting the text on the Save-Button

{
    "de": {
        "CORE_SAVE": "Abspeichern"
    },
    "en": {
        "CORE_SAVE": "Store"
    }
}

Remove translation

A translation can only be removed in the JSON editor in the Core Service Settings (see Core Services settings).

Show/hide columns in the language key list

If languages other than German and English have been created, these can also be displayed in the list of translation keys.

Move the mouse pointer over any column header.
Arrow for the drop-down menu appears.
Open the drop-down menu.
select "Columns".
Check or uncheck the desired columns.
Save.

Arrange columns

The order of the columns is alphabetical by default - apart from the "Name" column, which is at the top.
The columns can be arranged individually using drag & drop.

The arrangement is only retained in the current session.
As soon as the page is reloaded or the user is logged out, the default order is restored.

Add your own language key

This function is only useful if you have at least one individually developed module for your BPC. In addition, the corresponding translation keys must be created in this module.
If necessary, consult your module developer about this.

Create additional language key

Click on "Add language key" in the toolbar.
A window opens.
Enter the name of the language key.

The same name must be selected here as is stored on the component.
Select the language for the translation.
Enter the translation.
Save.

Edit language key

Edit translation

Select the language key in the list.
All languages and translations contained in the language key are displayed.
Adapt the translation in the desired language editor.

Edit the name of a self-created language key

To Core Service Settings change.
In the setting Core_CustomTranslations, adjust the corresponding key in the JSON editor.

Remove language key

Self-created language keys must be changed in the setting Core_CustomTranslations in the (see Core Service Settings) in the JSON editor.

Filter language keys and translations

If you are looking for a specific language key, you can filter the list.

Example:
To filter for a save button, you can enter "Save" in the filter field and then adjust the desired key based on the module assignment in the name.

Click on the "X" to delete all the text in the field.

Sort language keys and translations

Click on column header/name (1x = ascending, 2x = descending, 3x = default)
Example: 1x click on "German" → list is sorted alphabetically in ascending order according to the entries in the "German" column
Move the mouse pointer over the column header > arrow for drop-down menu > sort in ascending or descending order

Select fallback language

Suppose the user selects a specific language and no or incomplete translations of the language keys are available for this language. In this case, a fallback language can be selected: a language that is automatically selected if there is no translation for the language actually selected. This means that all texts with a translation are also displayed in a translated version and all texts without a translation are displayed in the fallback language.

Only one fallback language can be selected for all language keys.
English is usually the default setting.

You can also adjust the fallback language in the core Service Parameters Core_TranslationsFallbackLanguage, see Core Services settings.

Keywords: