Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ritcv.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!rochester!ritcv!spw2562
From: spw2562@ritcv.UUCP
Newsgroups: net.internat
Subject: Re: What do we REALLY want?
Message-ID: <9029@ritcv.UUCP>
Date: Wed, 13-Nov-85 15:05:13 EST
Article-I.D.: ritcv.9029
Posted: Wed Nov 13 15:05:13 1985
Date-Received: Fri, 15-Nov-85 08:31:15 EST
References: <723@inset.UUCP> <960@erix.UUCP> <1569@hammer.UUCP>
Reply-To: spw2562@ritcv.UUCP (Steve Wall ( spw2562 @ Rochester Institute of Mentality.. er Technology ))
Distribution: net
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 26

In article <422@graffiti.UUCP> peter@graffiti.UUCP (Peter da Silva) writes:
>	0xxxxxxx	  Normal ASCII
>	10xxxxxx	  Foreign ROMAN characters
>	11xxxxxx xxxxxxxx Kanji or other extended character
>...and just stuff all the foreign variants into the 64 extra characters this
>makes available for the purpose.
>I am sufficiently egocentric to believe that there is something to it...
>Name: Peter da Silva
>UUCP: ...!shell!{graffiti,baylor}!peter
>IAEF: ...!kitty!baylor!peter

This is a good idea - even if you are egocentric 8-).
Alternately, use a 16 bit code, as has been mentioned, keeping the lower byte
the same as the current ascii standard, but setting bits in the upper byte
to indicate using different varients of the base character.  This would
allow stripping the upper byte of to leave only 8 bits without changing which
basic character it is. As for totally unique characters, they could be
arbitrarily assigned.  If this has been suggested before, my apologies for
mentioning it again.  I just now started reading this newsgroup.

==============================================================================
	Steve Wall @ Rochester Institute of Technology
	USnail: 6675 Crosby Rd, Lockport, NY 14094
	Usenet:	...!ritcv!spw2562			Unix 4.2 BSD
	BITNET:	SPW2562@RITVAXC				VAX/VMS 4.2
	Voice:  Yell "Hey Steve!"