iso-8859-2 characters in gnome-terminal

[charon]

I'm having troubles with gnome-terminal. It does not display iso-8859-2 characters (some of them are displayed and instead of the others are there just whitespaces). Even if I choose czech as Gnome language at startup ...

My config is:
- gnome-terminal version 2.0.1
- export locales (LC_CTYPE="cs_CZ") in Gnome session
- -misc-fixed-bold-r-normal-*-*-140-*-*-c-*-iso8859-2 font (which was taken from working gnome1.4 configuration on my other RedHat desktop, but I tried other fonts too)

Weird is that other applications (both Gnome2 and Gnome1) are OK and display characters correctly ...

Any1 experienced and solved this ?

Thx for the advice ...
Charon

[KiTaSuMbA]

with iso-....-7 (modern greek). The strange thing is that I didn't have these problems on gnome2 before but only after a recent -u world. What, in the eyes of an end user, has changed is gcc3.2 and gnome-terms font selection method: instead of the classic gtk-font-select dialog you've got a roll-down menu with available fonts - according to the app (they appear to be far less than those I've got installed). No other gnome2 app seems to be having such troubles, so I assume it's a gnome-term specific bug.

<rant>
In the early days of linux DEs, it was KDE that looked and behaved "redmondish" and gnome offered more of the unix "user-controls-everything" philosophy. Starting with gnome 1.4 (that made me shift to independent window managers and just use some gnome-apps) and culminating to gnome2, there is an obvious inversion to this trend. Gnome appears to be chanting the well-known "you don't need to know how it works" and "I'll do it for you, without you" mantras. Personally, gnome is one bit away from losing its last components from my prefered apps list...
Farewell, G.N.O.M.E., it's been good while it lasted!
</rant>

____________________________
EDIT:
submitted bug #9759
_________________
Need to flame people LIVE on IRC? Join #gentoo-otw on freenode!

[KiTaSuMbA]

Ok, Spider rapidly replied (thnx! ) to the bug entry and it looks like there is nothing gentoo people can do to fix this but simply wait for gnome 2.2.

So, to put you out of the agony, here follows the relevant parts of the reply: