| Subject | Re: [Firebird-Architect] UTF-8 Everywhere |
|---|---|
| Author | Paul Vinkenoog |
| Post date | 2014-01-18T03:18:45Z |
Jim Starkey wrote:
endianness matters. The standard allows specifying the endianness like
this: UTF-16LE / UTF-16BE. But it's still one encoding, just like a
16-bit two's complement signed integer is one encoding. Endianness has
to do with storage, not encoding. (Still a pain in the ass though, but
one that we have learned to live with.)
Paul Vinkenoog
> What is the case for UTF-16?Much more efficient than UTF-8 for East-Asian languages.
> Or, more properly, what is the case for the two different UTF-16s?There's only one UTF-16, but because UTF-16 is made up of 2-byte words,
endianness matters. The standard allows specifying the endianness like
this: UTF-16LE / UTF-16BE. But it's still one encoding, just like a
16-bit two's complement signed integer is one encoding. Endianness has
to do with storage, not encoding. (Still a pain in the ass though, but
one that we have learned to live with.)
Paul Vinkenoog