From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Lex, Yacc, Unicode Plane 1
Date: Thu, 28 Jan 2010 18:42:45 -0500 [thread overview]
Message-ID: <1f4d3cc302892f8e9d9c788a0c3a7145@ladd.quanstro.net> (raw)
In-Reply-To: <3156d55fd27c66805eb5621e34222bb6@plan9.bell-labs.com>
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
next prev parent reply other threads:[~2010-01-28 23:42 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
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 [this message]
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=1f4d3cc302892f8e9d9c788a0c3a7145@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).