: > 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
Doesn't the font path only affect the order of directories, not single
font files?
: > 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.
This should be exactly what I do; I don't have 10x20 and 10x20u but
I just replaced the original fonts with the Unicode versions.
: 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,
Normal (non-wide) Unicode characters all work with my 10x20 setup.
: and it then tries
: to find an iso8859-1 font for the doublewide characters..
But as it works with you, at least the fonts themselves may have been
generated correctly, so I'll try further with X configuration (this is
on the Exceed X server for Windows, but I couldn't run the fonts at home
on Linux either).
Regards,
Thomas
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
