On Thu, Jan 24, 2002 at 04:25:10PM -0500, Dan Espen wrote:
> Olivier Chapuis <[EMAIL PROTECTED]> writes:
> > 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>
> > 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!
>
> I think you are suggesting to remove the 3 byte escape sequence
> when fvwm is compiled without multibyte.
> I've been meaning to do the same for a while but haven't
> had the chance.
>
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).
> 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?
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]
