From: Jim Choate <ravage@ssz.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan 9 (in)security
Date: Sun, 1 Jul 2001 21:03:34 -0500 [thread overview]
Message-ID: <Pine.LNX.3.96.1010701210144.24279d-100000@einstein.ssz.com> (raw)
In-Reply-To: <20010702013732.14EBA19A1A@mail.cse.psu.edu>
Don't simply re-create the errors of the past. Plan for the future.
Don't futz around with 64k of char, go for something like 32 bits or even
64 so that even in the future there won't be a significant effect as the
languages we use grow.
On Mon, 2 Jul 2001 okamoto@granite.cias.osakafu-u.ac.jp wrote:
> This is a multi-part message in MIME format.
> --upas-nuiiuxxrfozmxljuvcjoshbuyt
> Content-Disposition: inline
>
> Some says we need up to 60k chars for Japanese. However, I must say
> I don't know such huge number of Kanji which eceeds my memory capacity.
> Most of 64k chars may be in very limited use such in some ancient documents
> etc. :-) If "computer" must deal with all of those documents, yes, we may have
> to have 64k chars...
>
> The 16 bit limits will meet problem, in practical, to write person's name, some
> of which are named using wrong Kanji when all Japanese were permitted
> to have their own family name about 150 years ago. ^_^ Now, we cannot say
> it's wrong anymore. :-)
--
____________________________________________________________________
Whereof one cannot speak, thereof one must be silent.
Ludwig Wittgenstein
The Armadillo Group ,::////;::-. James Choate
Austin, Tx /:'///// ``::>/|/ ravage@ssz.com
www.ssz.com .', |||| `/( e\ 512-451-7087
-====~~mm-'`-```-mm --'-
--------------------------------------------------------------------
next prev parent reply other threads:[~2001-07-02 2:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 1:38 okamoto
2001-07-02 2:03 ` Jim Choate [this message]
2001-07-02 11:56 ` rob pike
2001-07-02 13:20 ` [9fans] " Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 18:10 [9fans] " David Gordon Hogan
2001-07-02 19:09 ` Dan Cross
2001-07-02 15:02 Sape Mullender
2001-07-02 15:52 ` Dan Cross
2001-07-02 16:24 ` Sam Ducksworth
2001-07-02 12:01 nigel
2001-07-02 12:05 ` George Michaelson
2001-07-02 12:07 ` rob pike
2001-05-27 15:00 rob pike
2001-05-27 4:27 rob pike
2001-05-27 6:43 ` Richard Elberger
2001-05-29 9:17 ` Douglas A. Gwyn
2001-06-29 9:23 ` Alex Danilo
2001-06-29 13:57 ` Douglas A. Gwyn
2001-06-29 21:08 ` Boyd Roberts
2001-05-27 0:52 Russ Cox
2001-05-26 23:02 jmk
2001-05-26 23:22 ` Alexander Viro
2001-05-26 19:54 Mike Haertel
2001-05-26 22:47 ` Alexander Viro
2001-05-26 23:23 ` Mike Haertel
2001-05-27 1:40 ` Alexander Viro
2001-05-28 4:40 ` Lucio De Re
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=Pine.LNX.3.96.1010701210144.24279d-100000@einstein.ssz.com \
--to=ravage@ssz.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).