From: "Hongzheng Wang" <wanghz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: [9fans] About The Codes Beyond Unicode-BMP
Date: Thu, 13 Mar 2008 22:28:54 +0800 [thread overview]
Message-ID: <b954b2060803130728v79b2933bq121ecdd430440766@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
Hi,
I did an experiment to test if the programs in Plan9 could support the
codes beyond Unicode-BMP.
The result is not so good.
Let's repeat it:
Take U+01000 code for example. Create a file and fill it with only
one character U+010000 encoded
in UTF-8.
Note that It is could be done with Vim on Linux since Vim has a good
support. Double check could
be done by Nvi. The internal representation of U+010000's with UTF-8
is F0908080 [1].
Open the file by ed or sam or acme. Of course, it could not be
displayed correctly since no fonts in
system could coverage such a code yet. Then, just re-write the file
again. Then open it again by
non-Plan9 program, say, Nvi on Linux. The internal representation became
EFBFBDEFBFBDEFBFBDEFBFBD. That is, both ed and sam (also acme) failed
to recognize
U+010000 encoded by UTF-8, and destroyed it when writing.
So, does Plan9 acctually supports only the codes in Unicode-BMP?
BTW: the attachment is the gzipped test file containing only U+010000
encoded by UTF-8.
[1] http://en.wikipedia.org/wiki/UTF-8
--
HZ
[-- Attachment #2: test.gz --]
[-- Type: application/x-gzip, Size: 30 bytes --]
next reply other threads:[~2008-03-13 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 14:28 Hongzheng Wang [this message]
2008-03-13 14:55 ` erik quanstrom
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=b954b2060803130728v79b2933bq121ecdd430440766@mail.gmail.com \
--to=wanghz@gmail.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).