From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <4B61E094020000CC0001D591@wlgw07.wlu.ca> Date: Thu, 28 Jan 2010 19:08:04 -0500 From: "Karljurgen Feuerherm" To: <9fans@9fans.net> References: <3156d55fd27c66805eb5621e34222bb6@plan9.bell-labs.com> <1f4d3cc302892f8e9d9c788a0c3a7145@ladd.quanstro.net> In-Reply-To: <1f4d3cc302892f8e9d9c788a0c3a7145@ladd.quanstro.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part93B9B7F4.0__=" Subject: Re: [9fans] Lex, Yacc, Unicode Plane 1 Topicbox-Message-UUID: ca1d2a7e-ead5-11e9-9d60-3106f5b1d025 This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=__Part93B9B7F4.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable thanks, erik. that's exactly right--we may or may not agree with Unicode = decisions, but the fact is some of poor slobs are stuck in the higher = planes whether we like it or not, so are looking for help... =20 erik, should we pursue the plan9port question offlist? it is going to take = me time to integrate info, no need to bog the list down in what is likely = to be simple for most folk... =20 (apologies if i'm not catching on as quickly as one might like...) =20 K >>> erik quanstrom 28/01/2010 6:42:45 pm >>> On Thu Jan 28 16:22:58 EST 2010, geoff@plan9.bell-labs.com wrote: > Yes, we only support the 16-bit runes of Unicode plane 0. That really > should be enough space, except for bungling by the Unicode Consortium. good point. at this point only ~21829 codepoints are assigned, depending on your definition of assigned. and i agree that the unicode consortium has taken a number decisions that make life difficult (unnecessary combiners and font-encodings for math characters are my pet peeves) . but now that the decision has been made, i think it makes sense to adapt, or at least put ourselves in the position to adapt. such a principled stance doesn't help someone who needs codepoints outside the basic plane. otherwise we become the 64000 characters ought to be enough for everyone guys. - erik --=__Part93B9B7F4.0__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Description: HTML
thanks, erik. that's exactly right--we may or may not agree with = Unicode decisions, but the fact is some of poor slobs are stuck in the = higher planes whether we like it or not, so are looking for help...
 
erik, should we pursue the plan9port question offlist? it is = going to take me time to integrate info, no need to bog the list down in = what is likely to be simple for most folk...
 
(apologies if i'm not catching on as quickly as one might like...)
 
K

>>> erik quanstrom <quanstro@quanstro.net> = 28/01/2010 6:42:45 pm >>>
On Thu Jan 28 16:22:58 EST 2010, = geoff@plan9.bell-labs.com wrote:
> Yes, we only support the 16-bit runes of Unicode = plane 0. That really
> should be enough space, except for bungling = by the Unicode Consortium.

good point.

at this point only = ~21829 codepoints are assigned, depending
on your definition of = assigned. and i agree that the unicode
consortium has taken a number = decisions that make life difficult
(unnecessary combiners and font-encod= ings for math characters
are my pet peeves) .

but now that the = decision has been made, i think it makes sense
to adapt, or at least = put ourselves in the position to adapt.
such a principled stance = doesn't help someone who needs
codepoints outside the basic plane.
otherwise we become the 64000 characters ought to
be enough for = everyone guys.

- erik

--=__Part93B9B7F4.0__=--