Internationalization (i18n) with language and locale codes

Language codes (only)

2-letter language codes from the ISO 639-1:2002 standard can cover most of the world's major languages and are used for all supplied UI-related and non-UI-related texts in Airlock IAM.

Adding/customizing languages:

  • Airlock IAM comes preconfigured with major European languages. The text strings are stored in UTF-8 encoded properties files for each language, e.g. en.properties (Loginapp UI) or in different strings_en.properties for other IAM components.
  • Changes to the Loginapp UI can be made using the Loginapp Design Kit.
  • New languages or translations can be configured by adding and translating new properties files for the corresponding IAM components.
    • After adding a new properties language file, the corresponding 2-letter language code must also be added in the Config Editor under Language Settings for the Loginapp, Adminapp and Transaction Approval to make the language selectable by the user.

  • Example:

Language and locale code combinations

Internal locale-code handling support with 2-letter codes from the ISO 639-1:2002 standard is partially available in Airlock IAM.

This applies to:

  1. Loginapp UI texts that are configured using the Loginapp Design Kit and in *.properties files, e.g., es_VE.properties for Venezuelan Spanish.
  2. Loginapp REST API/Transaction Approval texts in strings_*.properties files, e.g., strings_es_VE.properties.
 
Functional limitation

Combinations of language and locale are not supported in the Adminapp UI and Service Container module.

An exception applies to maintenance messages: if a locale is provided, only the language portion is used.

If the language information is invalid, for example because of an invalid language code or an unsupported language-locale combination, the default language is used as fallback.

Localized translations for Loginapp UI and Transaction Approval require to be referenced in the language settings of the Config Editor:

  • After adding a new UTF-8 encoded properties language file, the corresponding 2-letter language code must also be added in the Config Editor under Language Settings to make the localized language selectable by the user.

  • Example:

  •  
    Notice

    Locales must be added to the language code separated by an underline i.e. es_VE (for Venezuelan Spanish) that will be parsed into i.e. es-va to match the requirements for Accept-Language HTTP request headers.

Further information and links

Internal links:

External links: