Subject: Re: wscons ioctl's
To: Bang Jun-Young <firstname.lastname@example.org>
From: Noriyuki Soda <email@example.com>
Date: 02/06/2002 23:57:19
>>>>> On Wed, 6 Feb 2002 23:31:05 +0900, Bang Jun-Young <firstname.lastname@example.org> said:
>> > > u_int16_t character; /* character */
>> Pardon my ignorance, you will know better: is u_int16_t realy enough here?
>> I haven't followed all the multibyte encoding discussions lately, but ISTR
>> there have been strong objections against "only" using UNICODE.
>> While there are multiple ways a character can be encoded when getting on the
>> screen, this interface defines only one way to get it back (and can not do
>> variable length encodings) - so the returned value should be unique.
> What does "variable length encodings" mean here?
UTF-16 requires 20bits for one character, and ISO-10646 requires
31bits. So, 16bits is not enough even for unicode...