From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] UTF-8 criticism?
Date: Sun, 18 Jul 2004 12:05:12 -0700 [thread overview]
Message-ID: <7359f049040718120571c93b25@mail.gmail.com> (raw)
In-Reply-To: <000701c46cf6$814c4370$92ec7d50@SOMA>
> that's not the real problem. it's implementing the collation
> sequences. the internal representation as 16 bit unsigneds
> is not a problem.
actually it is, now that surrogates are well-established.
-rob
next prev parent reply other threads:[~2004-07-18 19:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 17:31 Jack Johnson
2004-07-18 18:27 ` Rob Pike
2004-07-18 18:39 ` boyd, rounin
2004-07-18 19:05 ` Rob Pike [this message]
2004-07-18 19:06 ` boyd, rounin
2004-07-19 9:00 ` Douglas A. Gwyn
2004-07-19 15:34 ` Skip Tavakkolian
2004-07-18 19:34 ` boyd, rounin
2004-07-19 7:40 ` Charles Forsyth
2004-07-19 8:39 ` Geoff Collyer
2004-07-19 21:01 ` Joel Salomon
2004-07-19 21:22 ` boyd, rounin
2004-07-19 21:35 ` Joel Salomon
2004-07-19 21:56 ` Joel Salomon
2004-07-19 21:42 ` andrey mirtchovski
2004-07-19 21:43 ` Tengwar " Joel Salomon
2004-07-20 8:32 ` Douglas A. Gwyn
2004-07-19 21:35 ` rog
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=7359f049040718120571c93b25@mail.gmail.com \
--to=robpike@gmail.com \
--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).