From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <4B61C07B020000CC0001D530@wlgw07.wlu.ca> Date: Thu, 28 Jan 2010 16:51:07 -0500 From: "Karljurgen Feuerherm" To: <9fans@9fans.net> References: <4B61B461020000CC0001D4FA@wlgw07.wlu.ca> <3156d55fd27c66805eb5621e34222bb6@plan9.bell-labs.com> In-Reply-To: <3156d55fd27c66805eb5621e34222bb6@plan9.bell-labs.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part9CB6B8DB.0__=" Subject: Re: [9fans] Lex, Yacc, Unicode Plane 1 Topicbox-Message-UUID: c9dee458-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. --=__Part9CB6B8DB.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Well.... having worked with the Unicode Consortium, I know there's a = little more to it than that... :) =20 But it's ok. If I have to write a preprocessor to make it work on Plan9, I = might as well stay with the Unix system currently available to me and = write a preprocessor for that. =20 I suppose I could use the PUA and write a postprocessor.... =20 Anyhow, thanks for the info. Now, at least, I know more clearly what my = options are. =20 K >>> 28/01/2010 4:20:41 pm >>> 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. --=__Part9CB6B8DB.0__= Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Description: HTML

Well.... having worked with the Unicode Consortium, I know there's a = little more to it than that... :)

But it's ok. If I have to write a preprocessor to make it work on = Plan9, I might as well stay with the Unix system currently available to me = and write a preprocessor for that.

I suppose I could use the PUA and write a postprocessor....

Anyhow, thanks for the info. Now, at least, I know more clearly what = my options are.

K

>>> <geoff@plan9.bell-labs.com> 28/01/2010 = 4:20:41 pm >>>
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.

--=__Part9CB6B8DB.0__=--