From: Rob Pike <robpike@gmail.com>
To: Skip Tavakkolian <fariborz.t@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Foreign-Language UNIX Efforts
Date: Wed, 22 Mar 2023 23:02:33 +1100 [thread overview]
Message-ID: <CAKzdPgwYPxK9oYemG5-vPgRR7mSfj_qkjD5-iJnLffP-23PUaQ@mail.gmail.com> (raw)
In-Reply-To: <CAA1C+h2KuP95QjvmnMCCgDsCbmXXU-bwnmTyryrH6KTdj7XjFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1424 bytes --]
The appendix version named it plain UTF, repurposing the extant name to the
new encoding. The -8 came later, as it is in these linked documents,
because some people wanted a UTF-7 and a UTF-16. Those people should be
punished.
-rob
On Wed, Mar 22, 2023 at 9:09 PM Skip Tavakkolian <fariborz.t@gmail.com>
wrote:
> Also here:
> https://github.com/0intro/plan9/tree/main/sys/doc
>
>
> On Wed, Mar 22, 2023, 3:02 AM Skip Tavakkolian <fariborz.t@gmail.com>
> wrote:
>
>> http://p9f.org/sys/doc/utf.ps
>>
>> On Wed, Mar 22, 2023, 12:41 AM <arnold@skeeve.com> wrote:
>>
>>> Thanks. Is there a link to postscript or pdf of the paper? I undoubtedly
>>> read it decades ago, but I doubt that I have it handy.
>>>
>>> Thanks,
>>>
>>> Arnold
>>>
>>> Rob Pike <robpike@gmail.com> wrote:
>>>
>>> > Pretty much, as it was the Plan 9 UTF man page at the time. This link
>>> will
>>> > be essentially the same.
>>> >
>>> > http://man.cat-v.org/plan_9/6/utf
>>> >
>>> > -rob
>>> >
>>> >
>>> > On Wed, Mar 22, 2023 at 6:12 PM Mehdi Sadeghi <mehdi@mehdix.org>
>>> wrote:
>>> >
>>> > > It's a long shot but is that appendix around by any chance?
>>> > >
>>> > >
>>> > > Mehdi
>>> > >
>>> > >
>>> > > On 3/22/23 03:52, Rob Pike wrote:
>>> > >
>>> > > the paper had an appendix that described UTF-8's encoding
>>> rigorously, but
>>> > > that was dropped
>>> > >
>>> > >
>>>
>>
[-- Attachment #2: Type: text/html, Size: 3201 bytes --]
next prev parent reply other threads:[~2023-03-22 12:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 5:00 [TUHS] " segaloco via TUHS
2023-03-19 13:32 ` [TUHS] " Diomidis Spinellis
2023-03-19 13:47 ` [TUHS] " Ralph Corderoy
2023-03-19 20:27 ` [TUHS] " Rob Pike
2023-03-20 7:55 ` arnold
2023-03-20 9:22 ` Rob Pike
2023-03-20 11:02 ` arnold
2023-03-20 15:44 ` Steffen Nurpmeso
2023-03-20 22:01 ` John Cowan
2023-03-20 22:28 ` Steffen Nurpmeso
2023-03-22 2:25 ` Larry McVoy
2023-03-22 2:52 ` Rob Pike
2023-03-22 7:12 ` Mehdi Sadeghi via TUHS
2023-03-22 7:33 ` Rob Pike
2023-03-22 7:40 ` arnold
2023-03-22 10:02 ` Skip Tavakkolian
2023-03-22 10:09 ` Skip Tavakkolian
2023-03-22 12:02 ` Rob Pike [this message]
2023-03-22 22:33 ` Steffen Nurpmeso
2023-03-22 23:33 ` segaloco via TUHS
2023-03-23 0:01 ` Warren Toomey via TUHS
2023-03-19 13:38 ` Edouard Klein
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=CAKzdPgwYPxK9oYemG5-vPgRR7mSfj_qkjD5-iJnLffP-23PUaQ@mail.gmail.com \
--to=robpike@gmail.com \
--cc=fariborz.t@gmail.com \
--cc=tuhs@tuhs.org \
/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).