On Fri, 25 Jan 2002, Olivier Chapuis wrote:
[SNIP]
> I am not sure that it is so easy to remove these "3 bytes" (which
> are not only 3 bytes and which can be found at different place
> in the string). Basically, we have to rewrite the
> XmbTextPropertyToTextList
> function (maybe in a weak form).
Hmmm... Those "3 bytes" (generally, much more) are ISO2022 escape
sequences. The 2022 is a very complex encoding (AFAIR, 2022 interpreter
is a state machine). It is documented somewhere, but those docs are hard
to read.
I'll ask Juliusz Chroboczek about how to strip 2022 tags in the
easiest way. But I'm sure the reply wouldn't be fast -- he is quite busy
with upcoming XFree 4.2.0 now.
> > I wouldn't use any Xmb function to do it though.
> > On Solaris, all the Xmb functions are in a separate shared
> > library. I think if you use that function you'll cause another
> > shared library to be loaded.
> >
> > I think the sequence is "Esc ( B" or "Esc B (" (I forget which).
> >
> > > Do I have to apply such changes to 2.4.5?
> >
> > Not for my benefit.
>
> Hum I do not know what we should do. But it seems that
> since the 2002-01-01 all the Europe (East and West) needs
> to use a locale with a non iso8859-1 charset. Also, I think
> that a lot of people outside of the Europe will want the
> EuroSign. The problem is not that people need the EuroSign
> in window titles, the problem is that if you use a charset
> != iso8859-1 and if the window title of an xterm (and of a lot
> of others programs) contains non ascii characters, then
> the window title is not displayed in the good way. The
> only thing that we can respond to this bug is "--enable-multibyte"
> (which is now my default). And there are problems with
> the I18N_MB patch.
>
> What you would say if you have to use --enable-multibyte
> for the "$" characters :o)
> We may add --enable-us? or --disable-8bits? :o)
>
> Really, I do not know what we should do. For 2.6.x
> we must improve the I18N_MB patch (and fix the utf8
> problem), but for 2.4.x?
YES. Definitely yes. Alexander had posted a screenshot with
cyrillic titles from XTerm -- you can see that the result is hardly
readable. The same happens with Netscape and almost all other apps --
they are correctly i18n'ed on Xlib layer.
BTW, while just stripping 2022 tags wouldn't be a "correct"
solution, it will work at least for koi8-r, iso8859-* and for other
singlebyte charsets.
The trick is that (at least in Russia) in case of locale with
"FOO-N" charset the fonts which are default (i.e. used by fvwm, first dir
in fontpath etc.) are *-FOO-N. And singlebyte encodings are represented
in 2022 "as-is" (e.g. koi8-r text is "<escape for koi8-r><that text in
koi8-r>"). So, we'll display FOO-N-encoded strings with FOO-N-font, which
is right. Of course, visiting chinese or even polish websites when in
russian locale will give funky titles, but that's what we had in old days.
_________________________________________
Dmitry Yu. Bolkhovityanov
The Budker Institute of Nuclear Physics
Novosibirsk, Russia
--
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]
