From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net From: "Russ Cox" Date: Thu, 13 Mar 2008 14:23:53 -0400 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Message-Id: <20080313182511.E33CF1E8C3A@holo.morphisms.net> Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] About The Codes Beyond Unicode-BMP Topicbox-Message-UUID: 783d9ec0-ead3-11e9-9d60-3106f5b1d025 > plan 9 supports utf16. that is codpoints u+0000 =E2=80=94 u+fffff. th= ere is no > support for 32bit characters.=20 this is correct except for the use of the term utf16, which is a character encoding, not a character set. the subject line is correct - plan 9 doesn't support codes beyond the BMP. > to support larger characters, the starting point > would be changing Rune from ushort to ulong and changing constants like > UTFmax and fixing chartorune and runetochar. (and finding all the plac= es > that assume that UTFmax really is 3.) > it's all very doable, but it would be a very invasive change. it would require recompiling everything,=20 but i don't believe it would require changes to code beyond the utf routines in the c library. i do not believe there are many places (if any) that presume to know the value of UTFmax. russ