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

ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSIONAnnex A: Character encoding informationNormativeField 1.015 Character encoding / DCS allows the user to specify the character set forcertain fields and record types, as described in Section 5.5. This Annex lists the codes forthe different characters commonly used.Several fields in the standard require Hexadecimal or Base-64 representations, which are alsodescribed in this annex.A.1: 7-bit ASCII7-bit ASCII is required for all fields in Record Type-1: Transaction information record. IfField 1.015 Character encoding / DCS is not included in the transaction, the default characterset encoding is 7-bit ASCII with the leftmost (eighth) bit padded with zero. ASCII is defined inANSI X3.4-1986 (R1992) (See Section 3 Normative references). See Table 108 for theallowed values.A.2: Unicode and UTF encodingField 1.015 Character encoding / DCS allows the user to select an alternate characterencoding listed in Table 4 Character encoding. UTF-8 and UTF-16 allow for the specialnational characters such as ü, é. ß and ñ. They also allow for certain other character sets, suchas Cyrillic and Arabic.Table 108 does not list all of these characters, only including a few examples. In Table 108,the character ç is in only the 8-bit Latin set, unlike the English language characters, whichare in both the 7-bit (default) character encoding set and the 8-bit set. The Chinese character白 is not in the 8-bit Latin character set, but it is in UTF-8. When using these extendedcharacter sets, they shall only appear where the record layout tables specify 'U' or 'userdefined'for the character type.UTF-8 encoding is variable width. The first 128 characters use one byte and areequivalent to US-ASCII. The next 1,920 characters require two bytes to encode. Threeand four bytes are also possible for certain, more rare characters. Note that the UTF-8and UTF-16 encodings are substantially different. Note: Table 108 shows UTF-16BE(Big Endian) values. It is recommended that UTF-8 be used in preference to UTF-16 orUTF-32.[2013n>] The code for the space was listed as being alphabetic in 2011. It ischanged to be a special character in this update, to bring the standard intoalignment with standard programming terminology. [