From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] About The Codes Beyond Unicode-BMP
Date: Thu, 13 Mar 2008 10:55:24 -0400 [thread overview]
Message-ID: <b615db319cecd764c8e0946fdc806c79@coraid.com> (raw)
In-Reply-To: <b954b2060803130728v79b2933bq121ecdd430440766@mail.gmail.com>
plan 9 supports utf16. that is codpoints u+0000 — u+fffff. there is no
support for 32bit characters. to support larger characters, the starting point
would be changing Rune from ushort to ulong and changing constants like
UTFmax and fixing chartorune and runetochar. (and finding all the places
that assume that UTFmax really is 3.)
it's all very doable, but it would be a very invasive change.
- erik
next prev parent reply other threads:[~2008-03-13 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 14:28 Hongzheng Wang
2008-03-13 14:55 ` erik quanstrom [this message]
2008-03-13 15:02 ` Hongzheng Wang
2008-03-13 18:23 ` Russ Cox
2008-03-13 18:38 ` erik quanstrom
2008-03-13 18:44 ` Joel C. Salomon
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=b615db319cecd764c8e0946fdc806c79@coraid.com \
--to=quanstro@coraid.com \
--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).