The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Ralph Corderoy <ralph@inputplus.co.uk>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Foreign-Language UNIX Efforts
Date: Mon, 20 Mar 2023 07:27:34 +1100	[thread overview]
Message-ID: <CAKzdPgxYPS3-XAJh2bzBRxSeJPO4tyietcNY+eyUvfYGR8fHow@mail.gmail.com> (raw)
In-Reply-To: <20230319134701.3A262220F7@orac.inputplus.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1644 bytes --]

As my mail quoted in
https://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt says,
Ken worked out a new packing that avoided all the problems with the
existing ones. He didn't alter Prosser's encoding. UTF-8, as it was later
called, was not based on anything but it was deeply informed by a couple of
years of work coming to grips with the problem of programming with
multibyte characters. What Prosser did do, and what we - all of us - are
very grateful for, is start the conversation about replacing UTF with
something practical.

(Speaking of design by committee, the multibyte stuff in C89 was atrocious,
and I heard was done in committee to get someone, perhaps the Japanese, to
sign off.)

Regarding windows, Nathan Myrhvold visited Bell Labs around this time, and
we tried to talk to him about this, but he wasn't interested, claiming they
had it all worked out. We later learned what he meant, and lamented. Not
the only time someone wasn't open to hear an idea that might be worth
hearing, but an educational one.

It's important historically to understand how all the forces came together
that day. The world was ready for a solution to international text, the
proposed character set was acceptable to most but the ASCII compatibility
issues were unbearable, the proposed solution to that was noxious, various
committees were starting to solve the problem in committee, leading to
technical briefs of varying quality, none right, and somehow a phone call
was made one afternoon to a couple of people who had been thinking and
working these issues for ages, one of whom was a genius. And it all worked
out, which is truly unusual.

-rob

[-- Attachment #2: Type: text/html, Size: 2621 bytes --]

  reply	other threads:[~2023-03-19 20:28 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     ` Rob Pike [this message]
2023-03-20  7:55       ` [TUHS] " 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
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=CAKzdPgxYPS3-XAJh2bzBRxSeJPO4tyietcNY+eyUvfYGR8fHow@mail.gmail.com \
    --to=robpike@gmail.com \
    --cc=ralph@inputplus.co.uk \
    --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).