From: "Karljurgen Feuerherm" <kfeuerherm@wlu.ca>
To: <9fans@9fans.net>
Subject: Re: [9fans] Lex, Yacc, Unicode Plane 1
Date: Thu, 28 Jan 2010 16:51:07 -0500 [thread overview]
Message-ID: <4B61C07B020000CC0001D530@wlgw07.wlu.ca> (raw)
In-Reply-To: <3156d55fd27c66805eb5621e34222bb6@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
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.
[-- Attachment #2: HTML --]
[-- Type: text/html, Size: 1027 bytes --]
next prev parent reply other threads:[~2010-01-28 21:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 19:43 Karljurgen Feuerherm
2010-01-28 20:05 ` erik quanstrom
2010-01-28 20:46 ` geoff
2010-01-28 20:59 ` Karljurgen Feuerherm
2010-01-28 21:20 ` geoff
2010-01-28 21:51 ` Karljurgen Feuerherm [this message]
2010-01-28 22:07 ` ron minnich
2010-01-28 22:19 ` hiro
2010-01-28 22:34 ` Karljurgen Feuerherm
2010-01-28 22:56 ` erik quanstrom
2010-01-28 23:38 ` Federico G. Benavento
2010-01-28 23:42 ` erik quanstrom
2010-01-29 0:08 ` Karljurgen Feuerherm
2010-01-29 0:19 ` Rob Pike
2010-01-29 0:24 ` erik quanstrom
2010-01-29 0:36 ` Russ Cox
2010-01-29 0:42 ` erik quanstrom
2010-01-29 0:58 ` Russ Cox
2010-01-29 6:08 ` erik quanstrom
2010-01-29 6:18 ` Justin Jackson
2010-01-29 14:36 ` Ethan Grammatikidis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B61C07B020000CC0001D530@wlgw07.wlu.ca \
--to=kfeuerherm@wlu.ca \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).