<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tt/onlinemanual/lan_conversions" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Conversions</Title>
		<Keyword ContextSensitive="No"><Level1>Language support</Level1>
			<Level2>conversion</Level2>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph class="Default">Character sets can have several encodings; a certain character is represented by an integer and that integer is converted to a certain encoding.</Paragraph>
		<Paragraph class="Default">Unicode for example has 3 standard encodings: UTF-8, UTF-16 and UTF-32.</Paragraph>
		<Paragraph class="Default">For Infor ERP LN a Unicode encoding is introduced that fits most with the current architecture. This encoding is called UTF-T and is in line with the TSS concept. TSS is the Infor ERP LN specific encoding for the other character sets.</Paragraph>
		<Paragraph class="Default">UTF-T is only used during runtime, that means that storage of data is always done in a standard encoding.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>UI</SectionTitle>
		<GeneralSection><SectionTitle>WorkTop/BW/BWPrint</SectionTitle>
			<Paragraph class="Default">These clients perform a conversion from Windows Unicode encoding to UTF-T or another TSS character set, dependent on the character set of the Infor ERP LN environment. So, communication between these clients and the back-end is in TSS format.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>WebTop</SectionTitle>
			<Paragraph class="Default">WebTop handles all data in Unicode and also passes the data to the back-end in standard UTF8. In the back-end the transformation to the TSS character set of the back-end (so, in case of Unicode to UTF-T) takes place.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection><SectionTitle>Reporting</SectionTitle>
		<GeneralSection><SectionTitle>Unix</SectionTitle>
			<Paragraph class="Default">In Unix the support for printing in various languages is very limited. The printer drivers, in contrast to Windows, provide very limited conversion support. Therefore the capabilities of the printer determine which languages can be supported.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Windows</SectionTitle>
			<Paragraph class="Default">In Windows the Infor ERP LN reports are printed via BWPrint. BWPrint converts to the Windows Unicode encoding and therefore any language can be printed.</Paragraph>
		</GeneralSection>
	</GeneralSection>
	<GeneralSection><SectionTitle>Integration via Adapter for Infor ERP LN
                           </SectionTitle>
		<Paragraph class="Default">The Adapter for Infor ERP LN communication is based on Unicode.</Paragraph>
	</GeneralSection>
	<GeneralSection><SectionTitle>
                              Infor ERP LN data export and import tools</SectionTitle>
		<Paragraph class="Default">The bdbpre and bdbpost tools will store the data in the intermediate file in ASCII format for single byte data, and in TSS format for multi-byte data. In a Unicode environment the data will be stored in UTF-T format.</Paragraph>
		<Paragraph class="Default">At this moment a dump generated on a single byte or multi-byte environment must always be imported in the context of the same locale (character set) as the original dump.</Paragraph>
	</GeneralSection>
</ManualTopic>
