| To translate software components |  |
| Multi-language Most ERP 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. ERP LN uses the Language Translation System (LTS) to both reduce the language-dependency of the ERP 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 ERP LN system contains, among other things: Form layouts and report layouts (one set for all languages) 2 sets of label descriptions, message descriptions and question descriptions. (Dutch and English) 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:
Language | Label description
Dutch | Volgnummer
English | Sequence No.
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 ERP 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: `high_ascii_tolerance:0` 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 ERP LN enables you to translate labels, questions and messages. Basic procedure Use the following sessions to translate the labels, questions and messages.: Labels (ttadv1140m000) Question Descriptions (ttadv4166m000) Message Descriptions (ttadv4150m000) Run the Compile Labels (ttadv1243m000) session to store the new label descriptions in the runtime data dictionary. 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.
Session | Description
Export Language Dependent Data to XML - Wizard (ttadv8910m000) | Use this session to export the components to XML files.
Merge Tool for XML-files with Language Dependent Components (ttadv8930m000) | Use this session to merge multiple XML files containing language-dependent components into one file.
Import Language-Dependent Data from XML - Wizard (ttadv8920m000) | Use this session to import the content of XML files containing language-dependent components into an ERP LN environment. Note: After you import the components, you must compile the labels.
Related topics Language Translation Support in the Infor Web Help |