<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tt/aad/ttaad1111m000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Data Languages (ttaad1111m000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to define <Link href="/baanerp/tt/glossary/glossary#100111" role="glossary" Update="No">Data Languages</Link>.</Paragraph>
			<Paragraph class="Default">You can define multiple data languages. You must mark one data language as the <Link href="/baanerp/tt/glossary/glossary#100110" role="glossary">Base Language</Link>. For details, refer to <Link href="/baanerp/tt/onlinemanual/mle_multi_language_application_data" role="manual">Multilanguage Application Data</Link>.</Paragraph>
			<Paragraph class="Default">A data language consists of an ISO 639-1 language code and, optionally, an ISO 3166-1 country code. See the following examples:</Paragraph>
			<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><THEAD><TR><TD width="69" rowspan="1" colspan="1">ISO 639-1 language code</TD>
						<TD width="76" rowspan="1" colspan="1">ISO 3166-1 country code</TD>
						<TD width="360" rowspan="1" colspan="1">Description</TD>
					</TR>
				</THEAD>
				<TBODY><TR><TD width="69" rowspan="1" colspan="1">de</TD>
						<TD width="76" rowspan="1" colspan="1"></TD>
						<TD width="360" rowspan="1" colspan="1">German</TD>
					</TR>
					<TR><TD width="69" rowspan="1" colspan="1">en</TD>
						<TD width="76" rowspan="1" colspan="1">GB</TD>
						<TD width="360" rowspan="1" colspan="1">English_UNITED KINGDOM</TD>
					</TR>
					<TR><TD width="69" rowspan="1" colspan="1">en</TD>
						<TD width="76" rowspan="1" colspan="1">US</TD>
						<TD width="360" rowspan="1" colspan="1">English_UNITED STATES</TD>
					</TR>
				</TBODY>
			</TABLE>
		</AimSection>
		<GeneralSection ID="life_cycle_of_a_data_language"><SectionTitle>Life cycle of a data language</SectionTitle>
			<Paragraph class="Default">Data Languages have a status which is used to control their life cycle.</Paragraph>
			<TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated"><TBODY><TR><TD rowspan="1" colspan="1">1</TD>
						<TD rowspan="1" colspan="1">New data languages have an initial status of "Pending for Addition". You can manually delete such data languages.</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">2</TD>
						<TD rowspan="1" colspan="1">You must mark one of the data languages, which are pending for addition, as the base language, before you can start the Convert Data Languages to Runtime process.</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">3</TD>
						<TD rowspan="1" colspan="1">When you convert data languages to runtime, all data languages with the status "Pending for Addition" get the status "Being Added".</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">4</TD>
						<TD rowspan="1" colspan="1">Once the Convert Data Languages to Runtime process succeeded, the data languages with status "Being Added" get the status "Available".</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">5</TD>
						<TD rowspan="1" colspan="1">You can mark "Available" data languages for removal. This sets the status to "Pending for Deletion". You can make such data languages available again, as no changes have yet been processed.</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">6</TD>
						<TD rowspan="1" colspan="1">When you convert data languages to runtime, all data languages with the status "Pending for Deletion" get the status "Being Deleted".</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">7</TD>
						<TD rowspan="1" colspan="1">Once the Convert Data Languages to Runtime succeeded, the data languages with status "Pending for Deletion" are deleted.</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">In Infor Enterprise Server versions prior to version 8.4.1, the coding of data languages is based on the ISO 639-2 standard. To use these data languages in Infor Enterprise Server 8.4.1 and higher, they must be migrated to the new ISO 639-1/ISO 3166-1 standard. After a conversion, these data languages have the "Migrated" status. For details, refer to <Link href="/baanerp/tt/onlinemanual/mle_to_migrate_data_languages" role="manual">To migrate data languages</Link>.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection ID="convert_data_languages_to_runtime"><SectionTitle>Convert data languages to runtime</SectionTitle>
			<Paragraph class="Default">You must use the <GUIRef href="/baanerp/tt/aad/ttaad1111m000#convert.to.runtime" role="command">Convert Data Languages to Runtime</GUIRef> command to (re)generate the $BSE/lib/data_langs file, which is used by the porting set at runtime. The process stores information, such as package combinations and languages processed, in a log file that you can print through the <GUIRef href="/baanerp/tt/aad/ttaad1111m000#show.log" role="command">Display Logfile</GUIRef> command.</Paragraph>
			<Important><SectionTitle>
                                    Important!
                                 </SectionTitle>
				<Paragraph class="Default">Use this command only if you are sure that you do not want to change the base language anymore. See the restrictions listed below. It is recommended to perform the conversion to runtime, after you have registered the multilanguage tables and fields.</Paragraph>
			</Important>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The <GUIRef href="/baanerp/tt/aad/ttaad1111m000#convert.to.runtime" role="command">Convert Data Languages to Runtime</GUIRef> command dumps the ISO 639-1/ISO 3166-1 data languages in the $BSE/lib/data_langs file, with a ‘_’ character as separator. So, for example, <Code>en_US</Code>.</Paragraph>
			</Note>
		</GeneralSection>
		<GeneralSection><List><ListTitle>Restrictions</ListTitle>
				<ListItem>You can fully maintain data languages as long as no Convert Data Languages to Runtime has ever been done.</ListItem>
				<ListItem>Once the first Convert Data Languages to Runtime has succeeded, you cannot change the base language anymore. However, you can still add data languages, which get the status "Pending for Addition" and mark data languages for deletion, which get the status "Pending for Deletion".</ListItem>
				<ListItem>You can only delete a data language, or mark a data language for deletion, if the language is not used in ERP LN. For example, you cannot delete a data language that is used in the <GUIRef href="/baanerp/tt/aad/ttaad1510m000" role="session">Software Languages (ttaad1510m000)</GUIRef> session or in the <GUIRef href="/baanerp/tt/aad/ttaad2500m000" role="session">User Data (ttaad2500m000)</GUIRef> session.</ListItem>
			</List>
		</GeneralSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/tt/onlinemanual/mle_multi_language_application_data" role="manual">Multilanguage Application Data</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="ttaad111.dlan"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Data Language</Title>
			</Header>
			<FuncDesc>An ISO 639-1 language code. For example: <Code>en</Code> (English) or <Code>fr</Code> (French).</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can zoom to the <GUIRef href="/baanerp/tt/aad/ttaad1512m000" role="session">ISO 639 Languages (ttaad1512m000)</GUIRef> session.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttaad111.icnt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Data Language</Title>
			</Header>
			<FuncDesc>An ISO 3166-1 country code. For example: <Code>GB</Code> (UNITED KINGDOM) or <Code>FR</Code> (FRANCE).</FuncDesc>
			<SimpleSection><Paragraph class="Default">The country code is optional.</Paragraph>
				<Paragraph class="Default">You can zoom to the <GUIRef href="/baanerp/tt/aad/ttaad1513m000" role="session">ISO 3166-1 Countries (ttaad1513m000)</GUIRef> session.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="ttaad111.stat"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Status</Title>
			</Header>
			<FuncDesc>The status of the language. For details, refer to <Link href="#life_cycle_of_a_data_language" role="internal">Life cycle of a data language</Link>.</FuncDesc>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="make.base"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Make Base Language</Title>
			</Header>
			<FuncDesc>Marks the selected language as the <Link href="/baanerp/tt/glossary/glossary#100110" role="glossary">Base Language</Link>. For details, refer to <Link href="#life_cycle_of_a_data_language" role="internal">Life cycle of a data language</Link>.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="mark.for.removal"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Mark for Removal</Title>
			</Header>
			<FuncDesc>Marks the selected language for removal. For details, refer to <Link href="#life_cycle_of_a_data_language" role="internal">Life cycle of a data language</Link>.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="make.available"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Make Available</Title>
			</Header>
			<FuncDesc>Makes the selected language available. For details, refer to <Link href="#life_cycle_of_a_data_language" role="internal">Life cycle of a data language</Link>.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="convert.to.runtime"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Convert Data Languages to Runtime</Title>
			</Header>
			<FuncDesc><Link href="#convert_data_languages_to_runtime" role="internal">Convert data languages to runtime</Link>
			</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="show.log"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Display Logfile</Title>
			</Header>
			<FuncDesc>Prints the contents of the log file generated by the <Link href="#convert_data_languages_to_runtime" role="internal">Convert data languages to runtime</Link> process.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
