Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: X on non-ASCII machines
Message-ID: <9009271323.AA10219@expire.lcs.mit.edu>
Date: 27 Sep 90 13:23:52 GMT
References: <188@thor.UUCP>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 14

Boy, am I glad you asked that question. :-)

We've recently been discussing this issue at some length inside the
X Consortium, as part of our work on internationalization.  The problem
is not really part of internationalization, but I view the root of the
problem and the piece of the solution as the same.  We're currently working
along the lines of having Xlib do all conversions automatically under the
covers, so that you can continue to use string literals and EBCDIC files,
and have everything work out reasonably well.  I won't guarantee you this
is how things will be specified, but I think that's where we're headed.

In the meantime, are you sure IBM doesn't have an Xlib product you can buy?
Because I suspect their Xlib, if they have it, is already reimplemented to
do such conversions.