The multi language management is responsible for changing the text IDs into strings that are presented to the user.
There are two translation aspects:
All literals in the GUI definitions of a layout are replaced by strings which are language-specific. This is based on the multi language management of Application Designer.
Note:
Detailed information on the multi language management is provided
in the Application Designer documentation at
http://documentation.softwareag.com/crossvision/cit/i18n/multilanguagemanagement.htm.
Literals that are contained in your application code are handled with the language management of Natural.
In a Natural for Ajax application, both language management systems are
related by common language codes. The language codes used are those that are
defined for the Natural profile parameter ULANG and the system
variable *LANGUAGE.
The Application Designer documentation describes how the text files containing the language-dependent texts are created and maintained (see the information on writing multi language layouts at the above URL). For a multi-lingual Natural for Ajax application, the names of the directories that contain the text files should be chosen according to the Natural language codes, for instance /multilanguage/4 for Spanish texts.
When an application is started from the Natural logon page, the user can select the language to be used. Depending on the selected language, the same (Natural) language code is set up both in Application Designer and in the Natural session, so that both language management systems are then configured to use the same language.
For compatibility with the predefined multi language directories in Application Designer, the English and German texts need not be stored in /multilanguage/1 and /multilanguage/2, but can be contained in /multilanguage/en and /multilanguage/de.
