Tomohiro KUBOTA wrote on 2001-05-14 10:20 UTC:
> > With the next version of xterm, it will also not be necessary any more
> > to specify an iso10646-1 font when you use UTF-8 mode. There will be
> > separate font resources such that you can specify fonts for both the
> > 8-bit and the 16-bit mode in your ~/.Xdefaults file
>
> Very good. BTW, what is 16-bit mode?
> (In Robert's and my patch, xterm has four modes of -8, -u8, -lc,
> and -en. If your "8-bit mode" means "-8" and "16-bit mode" means
> other three modes, I understand what you said. That implies that
> Robert's and my patch will be integrated in "the next version of
> xterm". Is it right? If yes, it is a very good news!)
I'm not sure, when Thomas and Robert plan to integrate their versions. I
fear it might be somewhat too late for XFree86 4.1, but don't know.
Robert? Thomas?
In essence, all these modes and command line options could be removed
now, at least under Linux, where everything can now be made locale
dependent. But perhaps some people will want to keep -u8 a bit longer
for use of UTF-8 xterm in environments that do not yet have UTF-8 locale
support (FreeBSD, etc.).
If it weren't for the stupid XFontStruct inefficiency, I would even
advocate to run xterm exclusively with iso10646 fonts and let the locale
handle all the conversion to the locale-dependent multibyte encodings
(like TCL/Tk is doing now). Keith's client side font library is probably
the solution out of this problem. The X server will then not touch fonts
at all and the XFontStruct mechanics becomes obsolete.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
