<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/EnterpriseStudio/onlinemanual/to_translate_software_components" xml:lang="en" TopicType="Overview">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">To translate software components</Title>
		<Keyword ContextSensitive="No"><Level1>
                                    Infor ERP LN Development Tools
                                 </Level1>
			<Level2>Translation</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>
                                    Infor ERP LN Development Tools
                                 </Level1>
			<Level2>Language Translation Support</Level2>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>
                                    Infor ERP LN Development Tools
                                 </Level1>
			<Level2>LTS</Level2>
		</Keyword>
	</Header>
	<GeneralSection ID=""><SectionTitle>Multi-language</SectionTitle>
		<Paragraph class="Default">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.</Paragraph>
		<Paragraph class="Default">
                                 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.</Paragraph>
		<Paragraph class="Default">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.</Paragraph>
		<Paragraph class="Default">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.</Paragraph>
		<ExampleSection><SectionTitle>
                                    Example
                                 </SectionTitle>
			<Paragraph class="Default">You use 2 system languages: Dutch and English.</Paragraph>
			<Paragraph class="Default">Your ERP LN system contains, among other things:</Paragraph>
			<List><ListItem>Form layouts and report layouts (one set for all languages)</ListItem>
				<ListItem>2 sets of label descriptions, message descriptions and question descriptions. (Dutch and English)</ListItem>
			</List>
			<Paragraph class="Default">The form of the <GUIRef href="" role="session">Add Session to Job (ttaad5102s000)</GUIRef> session contains a label ttaad320.seqn. The description of this label is stored in 2 languages:</Paragraph>
			<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><THEAD><TR><TD rowspan="1" colspan="1">Language</TD>
						<TD rowspan="1" colspan="1">Label description</TD>
					</TR>
				</THEAD>
				<TBODY><TR><TD rowspan="1" colspan="1">Dutch</TD>
						<TD rowspan="1" colspan="1">Volgnummer</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">English</TD>
						<TD rowspan="1" colspan="1">Sequence No.</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph class="Default">When a user runs the session, the label description is displayed depending on the user's language.</Paragraph>
		</ExampleSection>
		<GeneralSection><SectionTitle>High Ascii Tolerance</SectionTitle>
			<Paragraph class="Default">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 <Emphasis>high_ascii_tolerance</Emphasis> resource to 0.</Paragraph>
			<Paragraph class="Default">If <Emphasis>high_ascii_tolerance</Emphasis> is not set to 0, problems will occur when the delivered components are imported in Unicode environments.</Paragraph>
			<Paragraph class="Default">To set <Emphasis>high_ascii_tolerance</Emphasis> to 0, add the following line in the <Emphasis>$BSE/lib/defaults/all</Emphasis> file:</Paragraph>
			<Paragraph class="Default"><Code>high_ascii_tolerance:0</Code>
			</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<Important><SectionTitle>
                                 Important!
                              </SectionTitle>
		<Paragraph class="Default">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.</Paragraph>
	</Important>
	<GeneralSection><SectionTitle>To translate labels, questions and messages</SectionTitle>
		<Paragraph class="Default">
                                 ERP LN enables you to translate labels, questions and messages.</Paragraph>
		<GeneralSection><SectionTitle>Basic procedure</SectionTitle>
			<ProcedureList><ListItem>Use the following sessions to translate the labels, questions and messages.: <List><ListItem><GUIRef href="" role="session">Labels (ttadv1140m000)</GUIRef>
						</ListItem>
						<ListItem><GUIRef href="" role="session">Question Descriptions (ttadv4166m000)</GUIRef>
						</ListItem>
						<ListItem><GUIRef href="" role="session">Message Descriptions (ttadv4150m000)</GUIRef>
						</ListItem>
					</List>
				</ListItem>
				<ListItem>Run the <GUIRef href="" role="session">Compile Labels (ttadv1243m000)</GUIRef> session to store the new label descriptions in the runtime data dictionary.</ListItem>
			</ProcedureList>
		</GeneralSection>
		<GeneralSection><SectionTitle>Additional sessions</SectionTitle>
			<Paragraph class="Default">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.</Paragraph>
			<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><THEAD><TR><TD rowspan="1" colspan="1">Session</TD>
						<TD rowspan="1" colspan="1">Description</TD>
					</TR>
				</THEAD>
				<TBODY><TR><TD rowspan="1" colspan="1">
							<GUIRef href="" role="session">Export Language Dependent Data to XML - Wizard (ttadv8910m000)</GUIRef>
						</TD>
						<TD rowspan="1" colspan="1">
                                             Use this session to export the components to XML files.</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">
							<GUIRef href="" role="session">Merge Tool for XML-files with Language Dependent Components (ttadv8930m000)</GUIRef>
						</TD>
						<TD rowspan="1" colspan="1">
                                             Use this session to merge multiple XML files containing language-dependent components into one file.</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">
							<GUIRef href="" role="session">Import Language-Dependent Data from XML - Wizard (ttadv8920m000)</GUIRef>
						</TD>
						<TD rowspan="1" colspan="1">
                                             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.</TD>
					</TR>
				</TBODY>
			</TABLE>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
		<RelTopic><Emphasis>Language Translation Support</Emphasis> in the Infor Web Help
                              </RelTopic>
	</RelatedTopics>
</ManualTopic>
