set XTerm*utf8Title to true

On Mon, 3 Aug 2009, Imre Péntek wrote:

> Public bug reported:
>
> by default XTerm*utf8Title is set to false, however the byte sequences
> that will change the title bar are actually sent out in utf8, so I
> suggest to hard-wire this setting to true. Check the attached screenshot
> also. Thank you.
>
> ** Affects: xterm (Ubuntu)
> Importance: Undecided
> Status: New

sadly, the proper choice depends on the window manager (and probably
other factors). I left the default to match existing practice for that
reason.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Hello, the Ubuntu system generally is utf8 based. That 'Zenék' directory was created by the installer (when I created my user account), and it really means Music. So changing the setting I suggest you to change would only mean that XTerm wouldn't be an exception anymore. I encounter the current behaviour as an inconsistency (well, any window manager not using utf8 as the default encoding is also an inconsistency)
again:
imi@most:~$ echo $LANG
hu_HU.UTF-8

On Mon, 3 Aug 2009, Imre Péntek wrote:

> Hello, the Ubuntu system generally is utf8 based. That 'Zenék' directory was created by the installer (when I created my user account), and it really means Music. So changing the setting I suggest you to change would only mean that XTerm wouldn't be an exception anymore. I encounter the current behaviour as an inconsistency (well, any window manager not using utf8 as the default encoding is also an inconsistency)
> again:
> imi@most:~$ echo $LANG
> hu_HU.UTF-8
>
> --
> set XTerm*utf8Title to true

If I change a default setting, it's different from having the Ubuntu
packager change it...

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

Well, I reported an Ubuntu bug:
Where did you find the bug?:
Distribution: Ubuntu
package xterm

On Tue, 4 Aug 2009, Imre Péntek wrote:

> Well, I reported an Ubuntu bug:
> Where did you find the bug?:
> Distribution: Ubuntu
> package xterm

I maintain xterm upstream, and check bugs in various packages,
since as a rule, packagers do not bother to notify upstream.

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net

I was able to confirm this fixed it for uxterm by adding *utf8Title:true to the UXTerm resource file. I was not able to achieve the same result by adding it to the XTerm resource file, presumably because it lacks some setting for switching on utf8 support.

From what I read in the man pages, if utf8Title is set to true, it sounds like perhaps there are applications which are dependent on the traditional behavior. Since uxterm is documented as "xterm with utf8 support" whereas xterm is documented as "traditional behavior", this gives the impression that setting utf8Title to true for uxterm and leaving it default (false) for xterm would be the most appropriate solution.

This bug was fixed in the package xterm - 253-1ubuntu1

---------------
xterm (253-1ubuntu1) lucid; urgency=low

  * Merge from Debian Unstable. (LP: #501150)
    + document in xterm manpage the limited availability of resources color16
      to color255 as noted in patch #188 (LP: #438850)
    Remaining Ubuntu changes:
    - Enabled URL highlighting
  * Add 100_uxterm_utf8_title.patch: Set utf8Titles to true by default
    when using uxterm, so that it displays utf8 directories in titles
    properly. May cause issues with apps that use control sequences for
    updating the xterm titlebar - users should use xterm or set utf8Title
    to false in this case.
    (LP: #320388, #408496)

xterm (253-1) unstable; urgency=low

  * New upstream release
    + parenthesize expression in MoreRows macro, fixing a limit check added in
      patch #251 (closes: #560039)
  * Update debian/copyright.
  * Add dependency on ${misc:Depends} (lintian).
  * Refresh patches 900_debian_xterm.diff and 901_xterm_manpage.diff.

xterm (251-1) unstable; urgency=low

  * New upstream release.
  * Update copy of XTerm FAQ to revision 1.107 (dated 2009/11/11).
  * Upstream introduced a new 'disallowedWindowOps' resource to fine-tune
    which operations are affected by the 'allowWindowOps' setting. After
    discussion with the security team, change the default for the new resource
    to include all operations.

xterm (250-1) unstable; urgency=low

  * New upstream release
    + add check and error-message for fonts that have no printable values in
      the ISO-8859-1 range (closes: #542434)
    + limit minimum cell-width for packed font to maximum-advance
      reported by Xft. Some fonts are wider than that, even in the Latin-1
      range (closes: #550497)
    + correct off-by-one in okPosition fix from patch #249 limit-checks which
      prevented double-click selection on the bottom line of the screen
      (closes: #550368)
    + document in xterm manpage the limited availability of resources color16
      to color255 as noted in patch #188 (LP: #438850)

xterm (249-1) unstable; urgency=low

  * New upstream release.
    + add limit-checks for result of visual_width() function, needed from
      patch #242 and exposed by #244 changes (closes: #548321).
  * Upstream changed the default of AllowWindowOps to false, remove patch
    903_windowops.diff.
  * Use the upstream default for pointerMode; drop patch
    902_pointermode_never.diff.

xterm (248-1) unstable; urgency=low

  * New upstream release
    + correct logic used to improve performance of missing-glyph check, which
      did not handle line-drawing characters (closes: #545220)

xterm (247-1) unstable; urgency=low

  * New upstream release.
  * Bump Standards-Version to 3.8.3.
  * Remove David Martínez Moreno from Uploaders as he hasn't been active on
    this package lately.
  * Kill remaining subversion $Id$ tags from debian packaging files.
  * Use libutempter, remove setgid bit from the xterm binary (closes: #537867).

xterm (246-1) unstable; urgency=low

  * New upstream release
    + interaction between allowSendEvents and the various allowXXXOps
      resources clarified in manpage (closes: #53...