Kevin Kofler wrote:
All this is because they consider UTF-8 to be "not invented here" and are
trying to change everything to use UTF-16 at the expense of backwards
compatibility and standards rather than just changing their default system
codepage to UTF-8 as everyone else (GNU/Linux, OS X etc.) did (and yes,
they do have support for variable-length system codepages already, the
Asian versions use that, they just don't want to use it for UTF-8).
I think it's more than that. They're deeply (and I mean *deeply*) in
denial that UTF-16 isn't a 16-bit fixed-length character set, because
they set up *so much* around it.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.