Olivier Chapuis <[EMAIL PROTECTED]> writes: > 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).
Maybe in theory the 3 bytes can occur anywhere, but every time I've seen them, they are at the start of the string. Java, for example, will put them there when you set the locale to en_Us. I think, if you have true multibyte strings, they might be anywhere, but when an application is just marking a string as multibyte, just in case, they seem to only be at the start of the string. > > > 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? Hey, I'm old fashioned, in my opinion, proportional fonts should never have been implemented on computers. I'm not even sure lower case makes any sense. 6 bit characters made more sense to me. IF I HAD MY WAY, EMAIL WOULD LOOK LIKE THIS. :) I don't think everyone understood your question. Current FVWM development is mainly on the 2.5.x branch. We don't know exactly when the 2.5.x branch will be ready, so we are making critical patches to the next 2.4.x release, 2.4.5. The question is should this change be applied to both branches or can it wait for the release of 2.6.0. I understand that people in other countries might have a different view about how badly they need better character set support. -- Dan Espen 444 Hoes Lane Room RRC 1C-214 E-mail: [EMAIL PROTECTED] Piscataway, NJ 08854 Phone: (732) 699-5570 -- 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]
