On Thu, 17 Aug 2000 [EMAIL PROTECTED] wrote:
> With a 9x18 xterm, it takes double-width characters from 18x18ja and
> everything works fine. With a 10x20 xterm, it seems to take double-width
> characters from the "ko" font (judged by shape) (why this difference?),
probably order in the font path
> and it does not work: the double-width characters are displayed in single
> width.
With your 20x20 fonts, in the font path, I can do xterm -u8 -fn
10x20u, and it works. If, however, I run xterm and choose "Huge", it
doesn't work at all - the 10x20 fonts get fished out instead of the
10x20u font, so no >256 characters get displayed, and it then tries
to find an iso8859-1 font for the doublewide characters..
This can be fixed by having
XTerm*VT100*font2: 5x7u
XTerm*VT100*font3: 6x10u
XTerm*VT100*font4: 7x13u
XTerm*VT100*font5: 9x15u
XTerm*VT100*font6: 10x20u
in my .Xdefaults.
I don't think this is a good solution to go into xterm, though. It needs
to be able to fall back to the non-unicode fonts if needed.
--
Robert
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
