https://bugzilla.novell.com/show_bug.cgi?id=464930
User mfabian@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=464930#c21
--- Comment #21 from Mike Fabian 2009-01-29 06:39:16 MST ---
I’ve added Thomas Dickey, xterm author to the CC: because I want to
change the openSUSE default of the ximFont xterm-Resource to
"fixed". "fixed" sounds like a silly value for a XIM fontset because
it doesn’t match any CJK fonts at all, nevertheless it seems to work
fine for at least scim and kinput2.
1) scim doesn’t use the fontset at all, it displays the preedit strings with
GTK, using "*".
2) kinput2 does use the fontset although it also has its own resources for the
fonts to use:
Kinput2*font: -*-fixed-medium-r-normal--16-*-*-*-c-*-iso8859-1
Kinput2*kanjiFont:
-*-fixed-medium-r-normal--16-*-*-*-c-*-jisx0208.1983-0
Kinput2*kanaFont:
-*-fixed-medium-r-normal--16-*-*-*-c-*-jisx0201.1976-0
XMODIFIERS=@im=kinput2 xterm -fx fixed
apparently forces kinput2 to use its own font settings instead of
the fontset supplied by xterm because the fontset supplied by xterm
is not usable for Japanese. kinput2 still works fine then supplying
the "*" fontset doesn't seem to improve anything. Supplying
fontsets from xterm with the ximFont resource may change the size
of the fonts used in the preedit string but with just "*" the
results seem to be pretty random depending on what happens to be
available and is matched first, it does not help to match the font
size used by xterm.
I.e. at least for scim and kinput2, using "*" for ximFont improves
nothing compared to "fixed" and just slows up the startup
extremely for zh_CH.UTF-8 and zh_HK.UTF-8 locales.
Using "fixed" for ximFont *may* cause problems for some legacy XIM
servers (as it works for kinput2 it is likely that it works for most
older XIM servers as well. But there *may* be some very old XIM servers
which can't handle this, I don't know). But as scim is the default on
openSUSE I think using "fixed" here is a better default for openSUSE.
Whether this would be a good default for upstream xterm I cannot say.
The other alternative to fix this slow startup would be to remove
the GBK and Big5HKSCS charsets from the respective XLC_LOCALE files.
There are very few fonts supporting these charsets anyway and
apparently no free fonts at all.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.