To translate software componentsIn LN you can export the labels, questions, and messages from a development or translation system and import them into other LN environments. Export and import of labels is performed by using XML-formatted files. Every XML file contains a selection of translatable components based on the user’s settings. The translated language files can be imported back into the Infor environment. The import process includes a conversion to runtime. All descriptions are stored as labels which can be handled by the same import and export processes. Multi-language Most LN implementations use several system languages simultaneously. In addition, various languages for user reports such as customer facing documents sometimes also require languages other than the local languages used. LN uses the Language Translation System (LTS) to both reduce the language-dependency of the LN applications and to lower the costs of media creation. Translatable software components, such as labels, questions, and messages, are stored separate from language-independent software components, such as form and report designs. The descriptions of the translatable software components are stored per language. Language-independent components contain only references to translatable components. E.g. a form layout or a report layout contains label codes, and a UI script can contain message codes or question codes. The descriptions of the labels, messages and questions are read at runtime, depending on the language of the user. Example You use 2 system languages: Dutch and English. Your LN system contains, among other things:
The form of the Add Session to Job (ttaad5102s000) session contains a label ttaad320.seqn. The description of this label is stored in 2 languages:
When a user runs the session, the label description is displayed depending on the user's language. High Ascii Tolerance If you plan to deliver software components or translations from your LN environment and your environment does not run in Unicode mode, you must set the high_ascii_tolerance resource to 0. If high_ascii_tolerance is not set to 0, problems will occur when the delivered components are imported in Unicode environments. To set high_ascii_tolerance to 0, add the following line in the $BSE/lib/defaults/all file:
Important! The sections below describe the sessions that you must use to translate software components. However, they do not describe all details of these sessions. For detailed session information, refer to the Infor Web Help. To translate labels, questions and messages LN enables you to translate labels, questions and messages. Basic procedure
Additional sessions The following sessions are useful if you want to distribute translated components from a translation/development system to other systems, or if you want to perform the translation in an external application, e.g. in a professional translation application such as Transit.
| |||||||||||||||||