From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan 9 (in)security
Date: Mon, 2 Jul 2001 13:01:18 +0100 [thread overview]
Message-ID: <E15H2OR-000Nak-0Y@anchor-post-34.mail.demon.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 89 bytes --]
I'm not sure 16 bytes is enough to code up the header.
You did mean it to be in xml?
[-- Attachment #2: Type: message/rfc822, Size: 1698 bytes --]
From: "rob pike" <rob@plan9.bell-labs.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 (in)security
Date: Mon, 2 Jul 2001 07:56:46 -0400
Message-ID: <0a0a01c102ee$135823e0$41734e81@oemcomputer>
Why stop at 64 bits per character? Why not go for 256, a 16x16
dot matrix of the ISO image for the character. Perhaps with a
16-byte header with special information such as case, dialect,
diacritical marks, etc.
-rob
next reply other threads:[~2001-07-02 12:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 12:01 nigel [this message]
2001-07-02 12:05 ` George Michaelson
2001-07-02 12:07 ` rob pike
-- strict thread matches above, loose matches on Subject: below --
2001-07-02 18:10 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 1:38 okamoto
2001-07-02 2:03 ` Jim Choate
2001-07-02 11:56 ` 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=E15H2OR-000Nak-0Y@anchor-post-34.mail.demon.net \
--to=nigel@9fs.org \
--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).