--kfjH4zxOES6UT95V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 06, 2002 at 11:57:19PM +0900, Noriyuki Soda wrote:
> >>>>> On Wed, 6 Feb 2002 23:31:05 +0900, Bang Jun-Young <junyoung@mogua.c=
om> said:
>=20
> >> > > 	u_int16_t character;			/* character */
> >>=20
> >> Pardon my ignorance, you will know better: is u_int16_t realy enough h=
ere?
> >> I haven't followed all the multibyte encoding discussions lately, but =
ISTR
> >> there have been strong objections against "only" using UNICODE.
> >>=20
> >> 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 no=
t do
> >> variable length encodings) - so the returned value should be unique.
>=20
> > What does "variable length encodings" mean here?=20
>=20
> UTF-16 requires 20bits for one character, and ISO-10646 requires
> 31bits. So, 16bits is not enough even for unicode...

Ok, so a: long character would be better, isn't it?

Thanks.

> --
> soda

--=20
Of course it runs NetBSD - http://www.netbsd.org
Julio Merino (Slink) <juli@merino.net>

--kfjH4zxOES6UT95V
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE8YaI/zz00ZOPKycwRAirnAJ9gwuu6oBDO/vtulD18RSangDc7rwCfUwa3
Gu5eM+12/+nOdgBBe+GgTWw=
=3tn5
-----END PGP SIGNATURE-----

--kfjH4zxOES6UT95V--