Localizing an Application with the Single Language Localization Method

Prerequisites

Address the following items prior to following this procedure:

  • The override files ClientText.ini, ApplicationText.ini, and Globals.ini must exist with the translated or overridden values. These files must be based on the localization base files generated for the current version of the application.

  • Verify the values for the configuration options ApplicationStringsFile, ApplicationGlobalsFile, and ClientStringsFile in the section [Configuration] of the server’s Agentry.ini file. If a disparity exists between these settings and the file names, change either the settings or the file names so that both match. Accomplish this by either viewing and modifying the Agentry.ini file directly, or by using the Agentry Administration client. If changes are made to the Agentry.ini file directly, make a backup copy prior to modifying the file.

Context

Use this procedure to localize an application using the single language localization method (ex: when translating an application’s client UI into a different language from the one in which it was developed.) You can combine this procedure with the multi-language localization method if needed. However, that process is not discussed here, with the focus on the single language method of localization.

This procedure is applicable for both language translation, as well as other localization requirements related to terminology or user interface overrides.

Procedure

  1. Copy the translated or localized versions of the localization override files to the folder for the server instance for your application, for example, C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\<AppName>.
  2. Restart the server so that the localization files are read in.
  3. Clients must perform a transmit with the server to receive the user interface definitions with the override values displayed.

Results

Once this procedure is complete, the clients will display the overridden, localized values on all related user interface components.