Localization and Internationalization

You can localize different objects in the Hybrid App Designer, such as the names of screen controls, screens, and mobile business objects.

You can localize the Hybrid App by creating locale properties files. You can then load, update, and generate localized Hybrid Apps.

All the localizable strings in the Hybrid App Designer XML model work as resource keys in the localization properties file. All the localization properties files are in the same directory as the Hybrid App packages (.xbw files).

Resource keys are divided into these categories, which include all the elements of the Hybrid App Designer XML model:

Localization consists of two levels of localization—the Hybrid App Designer XML model localization and the Hybrid App client localization.

All locale properties files are saved in the same directory as the Hybrid App package.

To ensure that the correct locale is picked up for the Hybrid Web Container, the following mechanism is used:

  1. If a precise match is found for language and country, for example, English - United States (en-us) is the locale and the file exists in html\en-us\hybridapp*.html, that file is used and the HTTP lang parameter is set to "en-us."
  2. If a precise match for country is not found, the language is used. For example, English (en). If the file exists in html\en\hybridapp*.html, that file is used and the HTTP lang parameter is set to "en."
  3. If a language match is not found, the default locale is used. If the file exists in html\default\hybridapp*.html, that file is used and the HTTP lang parameter is set to "default";
  4. If a default match is not found, no locale is used. If the file exists in html\hybridapp*.html, that file is used and the HTTP lang parameter is set to "".