On Thu, Jan 24, 2002 at 03:44:20PM +0300, Alexander Kotelnikov wrote:
> >>>>> On Thu, 24 Jan 2002 13:02:54 +0100
> >>>>> "Olivier" == Olivier Chapuis <[EMAIL PROTECTED]> wrote:
> Olivier>
> >> Hmm... you could trust me, if it still works, it will stop soon, for
> >> me it looks like.
> >>
> >>
> >> The trouble is that window's title is not string of chars*, but
> >> multibyte srting.
> >>
> Olivier>
> Olivier> Ha, I see. koi-r fonts are not multibyte. The point here is
>
> koi8-r _charset_ fit 256 table
>
> Olivier> that some applications as xterm do strange things when it
> Olivier> has a title with certains characters (the EuroSign with
> Olivier> with iso-8859-15). Some other apps do not do that (E.g.,
> Olivier> rxvt, fvwm modules, fvwm menu). If we can find a document
> Olivier> on the strange thing that do xterm we will be able to
> Olivier> filter the bad characters that appear in your xterm window
> Olivier> title (in the !I18N_MB case).
>
> Ha! this is really great fault of these programs (rxvt fvwm and
> stuff), since KOI8-R locale consists of two character sets: koi8-r
> and... iso8859-1. So 1) there is not correct way keep KOI8-R strings
> in as ordinar char* 2) ther is no way to draw these strings with
> XDrawString.
>
Of course, fvwm ignore the locale when !I18N_MB. What I just claimed
is that fvwm and others app can display Russia characters without
any i18n support. The problem with xterm is that it is compiled
with i18n support and gives multibyte titles at once it see
a non ASCII characters (it will be better to do so when this
is really needed: when says there is both non ASCII "koi8-r chars" and
non ascii "iso8859-1 char"). My rxvt does not have the problem
because it is compiled without multibyte support but it cannot
gives window title with both non ascii "koi8-r chars" and non ascii
"iso18859-1 char" as xterm can (fvwm with I18N_MB).
Now I think that understand the problem.
So ok, KOI8-R locale is multibyte, but koi8-r fonts are not.
What fvwm2 can do without i18n support is to display koi8-r
strings, that's all, exactly as it can display iso8859-1 font
(it can display some window title (or menu) with koi8-r and
some other with iso8859-1). This work fine only with application
without i18n support. This seems consistent.
Now what we may want is to have by default a weak
multibyte support: just handle the xterm titles problems
(which arise with all the apps with i18n support).
Of course it will not possible to mix koi8-r and iso8859-1
and fonts should be explicitly set.
In fact this is easy to be done:
We just have to modify get_name_property in add_window.c
(the !I18N_MB one) and the corresponding code in events.c.
To filter the xterm titles it is enough to use
XmbTextPropertyToTextList
The solution of the filtering problems was simple!
Do I have to apply such changes to 2.4.5?
Olivier
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
