Followup to: <C110A2268F8DD111AA1A00805F85E58D0115AB26@ntgbg1>
By author: Karlsson Kent - keka <[EMAIL PROTECTED]>
In newsgroup: linux.utf8
>
> > We have now in wchar_t a nice infrastructure for handling 31-bit
> > characters, and I do urge all implementors of UTF-8 encoders and
> > decoders to keep them fully 31-bit transparent. UTF-16 is pretty
> > irrelevant to the GNU/POSIX platform. The wc API was not designed
> > to handle double-double-byte characters such as surrogate pairs.
> > Why should Linux programmers destroy the potentially useful full
> > 31-bit space, just because of silly interoperability concerns by
> > the UTF-16 crowd? They are
>
> Why are interoperability concerns "silly"? Do you plan to live in
> a Linux only world, never to communicate with systems running
> Windows, MacOS, Epoc, or any major database? (All employ UTF-16.)
>
They are silly because they are trying to "prevent interoperability
problems" for something that is inherently not interoperable anyway.
Of course, the fundamental problem is UTF-16 in the first place.
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
