This procedure describes how to localize an application using 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 SAP
Control Center.
If changes are made to the Agentry.ini file directly,
make a backup copy prior to modifying the file.
Task
Use this procedure 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 method if needed. However, this 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.
- Copy the translated or localized versions of the
localization override files to the folder for the Agentry
Server instance
for your application, i.e. C:\SAP\MobilePlatform\Servers\UnwiredServer\Repository\Agentry\default\<AppName>.
- Restart the Server so that the localization files are
read in.
- Clients must perform a transmit with the Server to receive
the user interface definitions with the override values displayed.
Once this procedure is complete, the Clients will display
the overridden, localized values on all related user interface components.