I was recently reminded of this one, and can see that it's no longer relevant:
+ The bug-report made incorrect assumptions about what xprop ought to be doing.
So it's not relevant to xprop.
+ Cloos' comment about xterm was interesting but not useful for xterm, because
the encoding as STRING rather than COMPOUND_STRING is done by the X Toolkit
library.
Reading the Shell.c file in libXt, arguably an application _could_ set the
resources titleEncoding and iconNameEncoding while setting the title and
icon-name, but even setting those to COMPOUND_STRING (which does _not_
hold UTF-8) wouldn'd make the server transmute those into EWMH names (which
_does_ hold UTF-8).
+ Regarding xterm, my changes in patch #349 make it do by default what Vincent
assumed.
Patch #349 - 2019/09/22
* improve title-string feature:
+ if any of allowC1Printable, utf8Title or titleModes hint that
an application might send a title-string encoded in UTF-8,
check if that is the case, and if it is recodable into
ISO-8859-1, use that for the ICCCM-style title.
+ check if the title given by a control sequence happens to be
already encoded in UTF-8, to avoid double-encoding (FreeBSD
#240393).
+ Make sameName resource work for the EWMH titles.
+ Modify menu-state of utf8Title to be consistent with the utf8
source, i.e., setting the EWMH properties automatically when
UTF-8 is active.
just for grins, I'll close this (expecting the usual response from Vincent).
--
Thomas E. Dickey <dic...@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
