Back Office translations¶
Enabling Back Office languages¶
All translations are available as a part of Ibexa DXP. To enable Back Office translations, use the following configuration:
1 2 3 4
Then clear the cache. Now you can reload your Ibexa DXP Back Office. If your browser language is set to French, the Back Office will be displayed in French.
Checking browser language
To make sure that a language is set in your browser, check if it is sent as an accepted language in the
You can also manually add the necessary .xliff files to an existing project.
Add the language to an array under
ibexa.system.<siteaccess>.user_preferences.additional_translations, for example:
ibexa.system.<siteaccess>.user_preferences.additional_translations: ['pl_PL', 'fr_FR']
composer run post-update-cmd and clear the cache.
Contributing Back Office translations¶
To learn how to contribute to a translation, see Contributing translations.
Selecting Back Office language¶
Once you have language packages enabled, you can switch the language of the Back Office in the User Settings menu.
Otherwise, the language will be selected based on the browser language.
If you do not have a language defined in the browser, the language will be selected
Custom string translations¶
When you extend the Back Office you often need to provide labels for new elements. It is good practice to provide your labels in translations files, instead of literally, so they can be reused and translated into other languages.
To provide label strings, make use of the
The method takes as arguments:
idof the message you want to translate
- an array of parameters
- domain of the string
Here's an example:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
The strings are provided in .xliff files.
The file should be stored in your project's or your bundle's
File name corresponds to the selected domain and the language, e.g.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
To provide a translation into another language, add it in the
For example, in
1 2 3 4 5
The language to display will then be selected automatically based on user preferences or browser setup.
You may need to clear the cache after adding new translations, before they are available in the Back Office.