On Thu, Jan 27, 2011 at 05:59:45PM +0300, Here I. Come wrote:
> > need more information to see if the referenced fix addresses user's
> configuration
>
> I've just checked that. Setting xterm.*utf8Title to true solves this
> bug, but by default this resource is unset(or set to false) with UTF-8
> locale
That is consistent with the manpage:
utf8Title (class Utf8Title)
Applications can set xterm's title by writing a control
sequence. Normally this control sequence follows the VT220
convention, which encodes the string in ISO-8859-1 and allows
for an 8-bit string terminator. If xterm is started in a UTF-8
locale, it translates the ISO-8859-1 string to UTF-8 to work
with the X libraries which assume the string is UTF-8.
However, some users may wish to write a title string encoded in
UTF-8. Set this resource to "true" to allow UTF-8 encoded
title strings. That cancels the translation to UTF-8, allowing
UTF-8 strings to be displayed as is.
Rephrasing, xterm normally expects that the title string is ISO-8859-1,
but can be told to accept UTF-8 instead.
--
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net
Attachment:
signature.asc
Description: Digital signature