[EMAIL PROTECTED] (Kai Henningsen) writes:
>> > * Do we need a "native" wide char encoding, too (mostly for Win32 where
>> > it's UTF-16, but possibly also some Asian thing)?
>>
>> A single 'char' encoded in UTF-16? This sounds horrible.
>
> I can't quite parse that.
If you've got a 16 bit wchar_t, there's no way that it can store
characters encoded in UTF-16. What happens to characters outside the
BMP?
16 bit wchar_t on C makes only sense in conjunction with UCS-2. All C
functions working on wide characters can only deal with characters in
the BMP anyway, even if you permit encoding wchar_t * strings in
UTF-16.
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
