Multi-Language Localization Method

This procedure describes how to localize an application using the multi-language method. Use this procedure when translating an application’s Client UI into one or more different languages from the one in which it was developed. You can combine this procedure with the single language method if needed. However, that process is not discussed here, with the focus on the multi-language method of localization.

Prerequisites

Address the following items prior to performing this procedure:

Determine the supported languages for the application and obtain the language names and locale names to match. For a complete list of locale names, see the URL:
```
http://msdn2.microsoft.com/en-us/library/ms776260(VS.85).aspx
```
Create or obtain the localization override files to use for each of the supported languages.
Determine the proper location to store the localization override files accessed by the Agentry Server. The default location is the sub-folder localizations of the Agentry Server’s installation location, though you can override this default location.
If the single language localization method is used to provide default override values, perform that procedure first.
Review the settings of the configuration options in the [Configuration] section of the Agentry.ini file, specifically:
```
ClientStringsFile
```
```
ApplicationStringsFile
```
```
ApplicationGlobalsFile
```

Task

Make a backup copy of the Agentry.ini configuration file and open it in a text editor.
Locate the section [Configuration] in this file. Set the value of the localizations option to contain a semicolon-delimited list of the locale names for the languages to support. If the localizations option is not listed it may be added. Following is an example of this option. It is set to provide support for two dialects of Spanish (Mexico and Span) and provide a default Spanish set of overrides: localizations=es-ES;es-MX;es.
If you are placing the localization files in a location other than the localizations sub-folder, set the configuration option localizationsPath to this location. If this option is not present, you can add it. If it is not necessary to override the default location, skip this step.
Verify the settings changed are accurate and close and save the Agentry.ini file.
Copy the localization override files to the localizations folder, or to the location specified in the localizationsPath configuration option and verify the names of these files match both the file name settings and the supported languages listed in the localizations option. Following is an example of the files needed based on support for Spanish as spoken in Spain, Mexico, and to provide a general Spanish set of overrides for other locales:

ApplicationText.es-ES.ini ClientText.es-ES.ini ApplicationGlobals.es-ES.ini ApplicationText.es-MX.ini ClientText.es-MX.ini ApplicationGlobals.es-MX.ini ApplicationText.es.ini ClientText.es.ini ApplicationGlobals.es.ini
Once this procedure is complete, restart the Agentry Server.

The new override values are read in during the restart.

Once this procedure is complete, the Agentry Server uses the locale information provided by the Agentry Clients to determine the proper override values, if any, to use. Those Agentry Clients with a locale not set to one of those listed in the localizations option receive the overrides in the single language localization files; or, if these are not in use, the values as defined in the published application project are sent to Agentry Clients by the Agentry Server.

Parent topic: Localizing Agentry Applications