Path: utzoo!mnetor!tmsoft!torsqnt!hybrid!scifi!bywater!arnor!kedalion.watson.ibm.com!dgreen
From: dgreen@arnor.uucp
Newsgroups: comp.windows.x
Subject: Re: Eight Bit Character Output to an Xterm window?
Message-ID: <1991Feb11.032816.6483@arnor.uucp>
Date: 11 Feb 91 03:28:16 GMT
References: <9102060936.AA05608@lightning.McRCIM.McGill.EDU>
Sender: news@arnor.uucp (NNTP News Poster)
Reply-To: dgreen@cs.ucla.edu
Organization: UCLA & IBM T.J.Watson Research Center
Lines: 30

mouse@lightning.mcrcim.mcgill.EDU writes:

|> > Xterm is written with ONE particular character set encoding in mind.
|> 
|> Not character set encoding so much as control sequence encoding.  It's
|> called ANSI X3.64, I believe.  If you read X3.64 and/or X3.41 (upon
|> which X3.64 is built), you will find something like

    ... control character spec ...

|> If you want to use xterm in an environment where 0x80-0x9f are supposed
|> to be considered printable, you should rework the whole control
|> sequence interpreter to conform to whatever standard is appropriate for
|> the environment in question, because it definitely isn't X3.64.

This doesn't seem very reasonable from an internationalization 
standpoint.  The set of printable characters should depend on some
specification in the app-defaults file, no?  (BTW, I am not using
an ISO 8859-1 character set.)

In any event, not being an internationalization expert, but trying to
produce an xterm for some british clients, I'm not exactly sure what
the control character set is there.

Time for a hack, I guess.  (Ugh.)  I hope R5 has a configurable display
character set for xterm.

____
\  /Dan Greening	IBM T.J.Watson Research Center	 NY (914) 784-7861
 \/ dgreen@ibm.com	Yorktown Heights, NY 10598-0704	 CA (213) 825-2266