Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!SUN.COM!guy
From: guy@SUN.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: Re: Telnet 8th bit: a good use for that bit...
Message-ID: <8702161934.AA00970@gorodish.wseng.sun.com.com>
Date: Mon, 16-Feb-87 14:34:22 EST
Article-I.D.: gorodish.8702161934.AA00970
Posted: Mon Feb 16 14:34:22 1987
Date-Received: Tue, 17-Feb-87 06:26:34 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 14
Approved: tcp-ip@sri-nic.arpa

> The Japanese standard (or at least one of them) is in some sense upward
> compatible with ASCII and European character sets.  Two byte sequences
> with both high order bits set are Kanji, single bytes with the high
> bit set are European.  Anything that might be a control character is
> always a control char, no matter what else surrounds it.

One of them - the UJIS code, as proposed by AT&T - is definitely
*not* compatible in this fashion; any byte with the 8th bit on,
unless preceded by an SS2, is either the first or second byte of a
two-byte Kanji (or Gaiji, but making *that* work would require TELNET
options to send fonts!) character.  Does the other one - Shift-JIS -
avoid all of the code points used by ISO Latin 1?  The UJIS code is
specified by the Sigma Project, and is being adopted by a number of
UNIX systems, at least, in Japan.