UTF-16: Perbedaan antara revisi

 

However UCS-2, UTF-8, and [[UTF-32]] can encode these code points in trivial and obvious ways, and large amounts of software does so even though the standard states that such arrangements should be treated as encoding errors. It is possible to unambiguously encode them in UTF-16 by using a code unit equal to the code point, as long as no sequence of two code units can be interpreted as a legal surrogate pair (that is, as long as a lead surrogate is never followed by a trail surrogate). The majority of UTF-16 encoder and decoder implementations translate between encodings as though this were the case.{{citation needed|date=October 2011}}<!-- Python 2.6 decode of UTF16 does this on Linux, and it correctly handles surrogate pairs. All "CESU" decoders do it too, though they also mistranslate correct surrogate pairs into 2 characters -->

==Byte order encoding schemes==