acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONIn order to ensure that the transaction description information can be read by all systems,data for all fields in Record Type-1 shall always be recorded in all encodings using thecharacters that can be represented by the 7-bit American National Standard Code forInformation Interchange (ASCII) found in Table 108 with the exception of the reservedvalues.The control characters “ F S” , “ G S”, “ R S”, “ U S”, “ STX ” and “ ETX ” are reserved characters in allencodings. Base-64 shall be used for converting non-ASCII text into ASCII form, whererequired and noted in the standard. (See Annex A: Character encoding information for adescription of Base-64).CharacterencodingindexCharacter encodingnameTable 4 Character encodingDescription0 ASCII7-bit (Default) with zero added in high bit position(See Annex A: Character encoding information)16 bit2 UTF-16 16 (See ISO/IEC 10646-1 and The Unicode standard)3 UTF-88-bit(See NWG 3629 and The Unicode standard)4 UTF-3232-bit(See The Unicode standard)5-127 ------------- Reserved for future use128-999 ------------- User-defined character encoding setsField 1.015 Character encoding / DCS is an optional field that allows the user tospecify an alternate character encoding. The default character encoding for Traditionalencoding is 7-bit ASCII. For XML, the default is UTF-8. Field 1.015 Characterencoding / DCS contains three information items: the character encoding set index /CSI, the character encoding set name / CSN, and the character encoding set version /CSV. The first two items (CSI and CSN) are selected from the appropriate columns ofTable 4. CSV specifies the specific version of the character encoding set used , such asUTF-8 version 1.0. Note that the value “1” does not appear in the table. It is a legacyvalue, which should not be used for newly generated transactions. The 2007 and 2008versions of this standard referred to it as “8-bit ASCII” and it was used to indicate theLatin-1 character set (ISO/IEC 8859-1).The 2007 version of the standard allowed users to switch any data (except that containedin the Type-1 record) to an alternative character encoding using a mechanism employingspecial control characters. This capability is retained in this version of the standard forTraditional encoding to ensure backward compatibility. See Annex B: Traditionalencoding. However, the 2007 version stated that for certain fields, UTF-8 could be used16In the 2007 and 2008 versions of the standard, this was called Unicode. It has been changed here forclarity, since Unicode can be expressed in UTF-8, UTF-16 and UTF-32 and code 2 only referred to UTF-16.May, 2013 DRAFT VERSION UPDATE 2013 Page 43