- From: Mark Davis <mark@macchiato.com>
- Date: Mon, 30 Jul 2001 09:25:09 -0700
- To: Harald Tveit Alvestrand <harald@alvestrand.no>, iana@iana.org, ietf-charsets@iana.org
Charset aliases: NONE Suitability for use in MIME text: NO Published specification(s): http://www.unicode.org/unicode/reports/tr19/ The IETF registration imposes one additional constraint: if there is no initial BOM then the byte-orientation must be big-endian. That is, in any stream that does not begin with the (hex) byte sequence <00 00 FE FF> all of the bytes are interpreted as big-endian. Note: This is parallel to the IETF registration of UTF-16. As defined by the Unicode Standard Version 3.1, without a BOM the byte orientation of UTF-32 and UTF-16 could be either little-endian or big-endian. The choice of byte orientation would be determined by a higher-level protocol. The IETF registration is such a protocol, and constrains the byte orientation to be big-endian for determinant interpretation. ISO 10646 equivalency table: Also in http://www.unicode.org/unicode/reports/tr19/ Additional information: Mark Davis 2509 Alpine Road, Menlo Park, CA 94025 mark@unicode.org Intended usage: LIMITED USE ]
Received on Wednesday, 1 August 2001 22:14:45 UTC