> plan 9 supports utf16.  that is codpoints u+0000 — u+fffff.  there is no
> support for 32bit characters. 

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 places
> 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, 
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


Reply via email to