From keld@dkuug.dk Sun Sep 29 00:40:50 1991
Received: by dkuug.dk (5.64+/8+bit/IDA-1.2.8)
	id AA01880; Sun, 29 Sep 91 00:40:50 +0200
Date: Sun, 29 Sep 91 00:40:50 +0200
From: Keld J|rn Simonsen <keld@dkuug.dk>
Message-Id: <9109282240.AA01880@dkuug.dk>
To: wg15rin@dkuug.dk
Subject: UniCode/10646
X-Charset: ASCII
X-Char-Esc: 29

Some info on 10646 and UNICODE, I think this summarises
the issue well. /keld

Date: Mon, 23 Sep 91 17:44:56 PDT
From: Bill.Tuthill@eng.sun.com (Bill "Bill" Tuthill)

People may or may not have heard that merger talks are underway
between Unicode and 10646.  These efforts are proceeding well,
and it looks like success is likely though not certain.  Here is
a quick summary of the situation:

 o  ISO 10646 will be a 32-bit code containing many languages,
	with room for more in the future.

 o  The first 8-bits will be upward compatible with ISO Latin-1,
	which implies ASCII compatibility.

 o  The first 16-bits, the Basic Multilingual Plane (BMP), will
	probably look a lot like Unicode.

 o  There will be a variable-length, "C0-safe" transmission code
	called AUC.  (I'm not sure what AUC stands for.)  AUC is
	algorithmic rather than table-driven.