Character encoding

From: Gavin Thomas Nicol <nick_at_nospam.org>
Date: Thu Oct 07 1993 - 16:13:41 PDT

>Was the *.sources posting from AT&T ?

No, the *.source posting was froma fellow at cray. It is the rune
system from BSD4.4.

>I know of some libXg/UTF2/runes/toolkit work happening at Sydney Uni.
>But I havent had a chance to chase up the guy doing it.
>[ Includes a "9term" or libg style xterm. ]

Yep, I have those. Actually, they are also available on research.att.com

>I was going to mail you (since you are working on MADO) and ask if you had
>or had seen:
> - the sam bundle
> - MGR
> - other ...

Yes, I have them all (except "other"?).

>What is EUC ?
>Does it handle codes not in Unicode ?
>If not provide a separate utf2<-->other library (runes ?) and just work
>in UTF2.

I'm not sure what the acronym is, but EUC is a character encoding
system in common use throughout Asia. It is a multibyte encoding
system. Along with that are JIS, SJIS, and a couple of others (though

>I have the Plan9 documnets and the postscript manual pages (broken into
>sections) online.

Me too. Actually, I meant Unicode mappings. Are the Unicode mapping
available online anywhere?

>> PS. I have plans (at some time or another) to include a FEP into the
>What is FEP ?

Front end processor. Things like Kanji cannot be entered from a normal
keyboard (because there are too many of them), so it is common to use
a FEP which allows you to enter romanised spellings of characters. The
FEP then translates it into normal Kanji/Kana. This could also be
useful for European languages. For example, by activating the FEP,
then typing a% (or perhaps phonetics), we get a with 2 dots over it.
Received on Thu Oct 7 16:19:36 1993

This archive was generated by hypermail 2.1.8 : Wed Sep 21 2005 - 19:37:12 PDT