…See [ ] [ Markus_Scherer csSCSU UTF-7 1012 RFC2152 RFC2152 csUTF7 UTF-16BE 1013 RFC2781 RFC2781 csUTF16BE UTF-16LE 1014 RFC2781 RFC2781 csUTF16LE UTF-16 1015 RFC2781 RFC2781 csUTF16 CESU-8 1016 Toby_Phipps csCESU8 csCESU-8 UTF-32 1017 Mark_Davis csUTF32 UTF-32BE 1018 Mark_Davis c…

…his document are to be interpreted as described in [ RFC2119 ]. As defined in [ RFC2781 ], the three charsets "utf-16", "utf-16le", and "utf-16be" are used to label UTF-16 text. In this document, "the UTF-16 family" refers to those three charsets. By contrast, the phrases "utf-16…

…See [ ] [ Markus_Scherer csSCSU UTF-7 1012 RFC2152 RFC2152 csUTF7 UTF-16BE 1013 RFC2781 RFC2781 csUTF16BE UTF-16LE 1014 RFC2781 RFC2781 csUTF16LE UTF-16 1015 RFC2781 RFC2781 csUTF16 CESU-8 1016 Toby_Phipps csCESU8 csCESU-8 UTF-32 1017 Mark_Davis csUTF32 UTF-32BE 1018 Mark_Davis c…

…See [ ] [ Markus_Scherer csSCSU UTF-7 1012 RFC2152 RFC2152 csUTF7 UTF-16BE 1013 RFC2781 RFC2781 csUTF16BE UTF-16LE 1014 RFC2781 RFC2781 csUTF16LE UTF-16 1015 RFC2781 RFC2781 csUTF16 CESU-8 1016 Toby_Phipps csCESU8 csCESU-8 UTF-32 1017 Mark_Davis csUTF32 UTF-32BE 1018 Mark_Davis c…

…nvert XML into UTF-8 MAY add a BOM. In addition to the MIME charset "utf-16", [ RFC2781 ] introduces "utf-16le" (little-endian) and "utf-16be" (big-endian). When an XML MIME entity is encoded in "utf-16le" or "utf-16be", it MUST NOT begin with the BOM but SHOULD contain an in-ban…

…epertoire. An example of this would be an XML document that uses the UTF-16LE [ RFC2781 ] encoding of [ Unicode ]. 2.1.1 . Formatting of Language Tags At all times, language tags and their subtags, including private use and extensions, are to be treated as case insensitive: there…

…¶ The format is defined using little-endian byte ordering (see Section 3.1 of [ RFC2781 ] ), but demuxing and decoding are possible on platforms using a different ordering with the appropriate conversion. The container is RIFF-based and allows extension via user defined chunks, b…

…ns The format is defined using little-endian byte ordering (see Section 3.1 of [RFC2781]), but demuxing and decoding are possible on platforms using a different ordering with the appropriate conversion. The container is based on RIFF and allows extension via user-defined chunks, …

…ns The format is defined using little-endian byte ordering (see Section 3.1 of [RFC2781]), but demuxing and decoding are possible on platforms using a different ordering with the appropriate conversion. The container is RIFF-based and allows extension via user defined chunks, but…

…repertoire. An example of this would be an XML document that uses the UTF-16LE [RFC2781] encoding of [Unicode]. 2.1.1. Formatting of Language Tags At all times, language tags and their subtags, including private use and extensions, are to be treated as case insensitive: there exi…

…epertoire. An example of this would be an XML document that uses the UTF-16LE [ RFC2781 ] encoding of [ Unicode ]. 2.1.1 . Formatting of Language Tags At all times, language tags and their subtags, including private use and extensions, are to be treated as case insensitive: there…

…epertoire. An example of this would be an XML document that uses the UTF-16LE [ RFC2781 ] encoding of [ Unicode ]. 2.1.1 . Formatting of Language Tags At all times, language tags and their subtags, including private use and extensions, are to be treated as case insensitive: there…

…epertoire. An example of this would be an XML document that uses the UTF-16LE [ RFC2781 ] encoding of [ Unicode ]. 2.1.1 . Formatting of Language Tags At all times, language tags and their subtags, including private use and extensions, are to be treated as case insensitive: there…

…epertoire. An example of this would be an XML document that uses the UTF-16LE [ RFC2781 ] encoding of [ Unicode ]. The tags and their subtags, including private use and extensions, are to be treated as case insensitive: there exist conventions for the capitalization of some of th…

…6LE UTF-16, UTF-16BE, and UTF-16LE, three transformation formats described in [ RFC2781 ] and defined in The Unicode Standard (Sections 3.9 and 16.8 of Version 6.0), are not required by any IETF standards, and are thus used much less often in protocols than UTF-8. Characters in t…