From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] strangely typed functions in standard library
Date: Thu, 18 May 2006 22:03:05 -0700 [thread overview]
Message-ID: <83c22f7e7be5837747428e6f2ca4ee47@collyer.net> (raw)
In-Reply-To: <6b8e7586eaf104fda388c17f4e43391b@quanstro.net>
I feel that the Unicode consortium bungled the job. People warned
them from the outset that 16 bits was a largish space, but still
finite. Once Han unification was done, the Unicode people felt that
they had all the room in the world, and assigned generous portions of
the space to each alphabet. Others warned them that they should be
more conservative in their allocations, but were waved off.
It may be that 16 bits are not enough to express all the necessary
characters in the world, but I don't think that the Unicode consortium
have proven that case.
next prev parent reply other threads:[~2006-05-19 5:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 3:06 erik quanstrom
2006-05-18 9:21 ` Bruce Ellis
2006-05-19 4:43 ` quanstro
2006-05-19 5:03 ` geoff [this message]
2006-05-19 12:43 ` Joel Salomon
2006-05-19 13:03 ` Victor Nazarov
-- strict thread matches above, loose matches on Subject: below --
2006-05-16 3:03 Matt Stewart
2006-05-16 11:40 ` Martin Neubauer
2006-05-16 15:09 ` R
2006-05-19 22:49 ` Lluís Batlle i Rossell
2006-05-19 22:43 ` quanstro
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=83c22f7e7be5837747428e6f2ca4ee47@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).