| # Conversions Character sets can have several encodings; a certain character is represented by an integer and that integer is converted to a certain encoding. Unicode for example has 3 standard encodings: UTF-8, UTF-16 and UTF-32. For Infor 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 LN specific encoding for the other character sets. UTF-T is only used during runtime, that means that storage of data is always done in a standard encoding. UI Worktop/BW/BWPrint 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 LN environment. So, communication between these clients and the back-end is in TSS format. Web UI Web UI 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. Reporting Unix 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. Windows In Windows the Infor LN reports are printed via BWPrint. BWPrint converts to the Windows Unicode encoding and therefore any language can be printed. Integration via Adapter for Infor LN The Adapter for Infor LN communication is based on Unicode. |