The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: tuhs@tuhs.org
Subject: [TUHS] Bell Foreign-Language UNIX Efforts
Date: Sun, 19 Mar 2023 13:47:01 +0000	[thread overview]
Message-ID: <20230319134701.3A262220F7@orac.inputplus.co.uk> (raw)
In-Reply-To: <d90865c0-7c1c-c726-83c2-a7114e31bf19@aueb.gr>

Hi Diomidis,

> The Bell Labs team took the bold approach of adopting the draft
> Unicode standard and an X-Open proposal for encoding multibyte
> characters only using bytes with the top bit set.  At the time the
> encoding was known as UTF-2; it is what we now call UTF-8.

Rob and Ken altered Dave Prosser's FSS-UTF rather than just adopting an
existing proposal, according to
https://en.wikipedia.org/wiki/UTF-8#History

More history, including Bell Labs emails from ’92:
https://www.cl.cam.ac.uk/~mgk25/ucs/utf-8-history.txt

-- 
Cheers, Ralph.

  reply	other threads:[~2023-03-19 13:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19  5:00 segaloco via TUHS
2023-03-19 13:32 ` [TUHS] " Diomidis Spinellis
2023-03-19 13:47   ` Ralph Corderoy [this message]
2023-03-19 20:27     ` 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
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=20230319134701.3A262220F7@orac.inputplus.co.uk \
    --to=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).