Agentry applications provide full support for localizing mobile applications without directly modifying the application project definitions. You can localize the application for one or more languages using localization override files, which replace the display values that are defined for the application. You can also use localization overrides for industry- or deployment-specific terminology.
To translate an application’s client UI into a language other than the one in which it was developed, the translator copies and modifies the localization base files to create override files that contain a localized version of the display values. These files are read and processed by the server during startup. The override values are then sent to clients during synchronization, after application definitions are synchronized but before production data is processed.
For single-language support, translators need to create only one set of override files. The single-language override files, which are specified in Management Cockpit, are used as the default override files if multiple languages are supported.
For multiple-language support, the translator creates additional override files, one for each locale that is supported by the application. The override file name must use the format <default_override_filename>.<locale_name>.ini. Copy the override files to the localization folder for the application. Specify the locales supported by the application and the localization folder for the override files in Management Cockpit.
The server uses the locale information provided by the Agentry clients to determine the proper override values, if any, to use. If the Agentry client locale setting does not match the supported locales for the application, the values from the default localization files are used. If no localization override files are specified, then the values that are defined in the published application project are sent to the client.
To modify localization files, update the files, and use Agentry Editor and Management Cockpit to publish a new version of the application. Do not update the configuration files on SAP Mobile Platform Server. Restart each server in a cluster to distribute the changes.