Translations
The OneWelcome Identity Platform supports the internationalization of templates via messages. For each message, multiple translations can be set. You can configure the translations of messages used in templates. These translations follow the i18n standard for messages.
Configure the supported languages
A translation can be configured for the locales supported by the OneWelcome Identity Platform. The supported locales can be configured via the admin console: System → General → Supported Locales.
Adding or updating a translation
When no translation is found for a message key, the OneWelcome Identity Platform looks for an available default. These defaults are available for the standard OneWelcome Identity Platform templates. When using custom templates, we advise picking different message keys per template set, so for these messages, no defaults are available without any configuration.
Configuration of a message key with corresponding translations is done by specifying the message key plus at least a default content. The default content is used if no matching translation is found for the user's language. For all supported locales, a separate content field is available to set the translation. If the content is left empty for a specific language, it is treated as unset, and the default is used. If, for example, English is your default language, but you also support Dutch, you only need to set the default and Dutch content, but not the English content. In this example, the default content is used for English.
If only a single locale is supported, this locale is seen as the default, so only the default content field is available.
For parametrized messages, use the {n} notation. To use, for example, the first provided parameter in your message: You have {0} attempts left.
Note
The translations are cached, so it can take some time before a change in a translation is reflected. The time-to-live for this cache can be configured via the cache configuration in the admin console.
Adding translations
Translations can be imported to the application by using the message files. Add property files to the template set in your git repository to make use of the customized translations. Refer to the default messages to further customize messages. These messages are used by the default templates.
- messages-engine.properties
- messages-engine_locale.properties
For example:
- messages-engine.properties
- messages-engine_nl.properties
- messages-engine_de.properties
Imported messages overwrite existing translations. Only the message files for the supported locales aree imported. These locales can be configured via
the admin console: System → General → Supported Locales. The file messages.properties must be present. This file contains the default
translations used when a specific translation is missing for a language.
Translation files
The translation files must follow the Java .properties file format. This means that each translation has a
key and a value separated by an equals sign: button.submit=Submit. Each translation must be placed on a new line. The length of each translation value is
limited to 1024 characters.
When the translation contains characters with diacritics (é, ü, ž) or special characters that are not present on a US keyboard, the safest option is to
convert them. Example: convert button.verify=Verifiëren into button.verify=Verifi\u00EBren
