On 22 Jan 2002 21:25:38 +0100, Olivier Chapuis wrote: > > Any way I do not understand why xterm considers > iso-8859-15 string as multibyte string if the string > contains non ascii characters (with an iso-8859-15 locale).
Someone said previously that this is not multibyte for one-byte non iso8859-1 charsets, but escape sequences containing charset as a hint. Maybe we should just write a filter that strips these escape sequences with --disable-multibyte, if we don't use this charset info anyway? > I do not know if we should close this bug report. I think > that we can put it in confirmed, do so that --enable-multibyte > can be the default and then close it. > > BTW, Mikhael, what about distributing i18n rpms? I would not double the number of rpms. Are --enable-multibyte problems easily solvable for it to be a default? If not, stripping escape sequences would be a good solution. Regards, MIkhael. -- 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]
