1.4 - Translations
To enable new locales, see the application distribution configuration. 🔗
For a given locale, the configurator will retrieve translated texts from multiple sources:
- The data from your products. See the product documentation 🔗 to know how to translate the content.
- The application's own translations. This page is dedicated to those translations.
Priorities and modifications​
When a text is displayed in the Product Configurator, the translation is searched in the following locations:
- Application Distribution translations 🔗
- Application translations 🔗
- Default translations 🔗
The first found translation is used.
1 - Application Distribution level​
When you set translations for a specific Application Distribution, they are only visible when using this specific Application Distribution.
You can use this API: Application Distribution Translations API. 🔗
You will need your Application Distribution ID, the locale you want to update, and your translations. 🔗
2 - Application level​
When you set translations for the application, they will be visible in all your Product Configurators. Keep the priorities in mind.
You can use this API: Application Translations API. 🔗
You will need the Application ID (13), the locale you want to update, and your translations. 🔗
3 - Default translations​
You cannot modify the default translations. They are available for the following language codes:
ar: Arabicde: Germanen: Englishes: Spanishfr: Frenchpt: Portuguese
If you need to translate the Product Configurator in another language, you can provide your own translations at application distribution or application level.
Structure​
All the translation keys used by the Product Configurator can be found here:
https://productconfigurator.enterprise.by.me/Environment/I18N/en.json 🔗
You can change all the available keys, or only override the ones you want to change. See the example below.
Example​
To simplify the example, we assume here that the file with all the translation keys contains the following:
{
"exampleKey": "Base translation 1",
"exampleKey2": "Base translation 2",
"exampleCategory": {
"exampleKey3": "Base translation 3"
}
}
If you want to override exampleKey and exampleCategory.exampleKey3 but keep the default translation for exampleKey2,
you would send the following JSON using our APIs:
{
"translations": {
"exampleKey": "Your customized translation 1",
"exampleCategory": {
"exampleKey3": "Your customized translation 3"
}
}
}