After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 321707 - gtk_set_window_title() should set WM_NAME even when a character is outside the WM charset
gtk_set_window_title() should set WM_NAME even when a character is outside th...
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
2.6.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 684239 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-11-17 10:30 UTC by Vincent Lefevre
Modified: 2014-09-16 07:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Lefevre 2005-11-17 10:30:37 UTC
Please describe the problem:
When a character is outside the WM charset (e.g. the Euro symbol when the WM is
in ISO-8859-1 locales), the WM_NAME property isn't modified by
gtk_set_window_title(). This is a problem with window managers like fvwm2 that
don't support _NET_WM_NAME. Non-representable characters should be replaced by a
"?" for instance.

Steps to reproduce:
1. Use ISO-8859-1 locales.
2. Start fvwm2.
3. Start Firefox.
4. Open a webpage with a Euro symbol, e.g.
<https://bugzilla.mozilla.org/attachment.cgi?id=202537>.

Actual results:
The window title after opening the page is still the old one; for instance,
xprop gives for the Firefox window:
WM_NAME(STRING) = "Bug 160236 - no window title if none of the *_NAME properties
are set - Mozilla Firefox"
_NET_WM_NAME(UTF8_STRING) = 0xe2, 0x82, 0xac, 0x20, 0x2d, 0x20, 0x4d, 0x6f,
0x7a, 0x69, 0x6c, 0x6c, 0x61, 0x20, 0x46, 0x69, 0x72, 0x65, 0x66, 0x6f, 0x78

Expected results:
WM_NAME should contain: "? - Mozilla Firefox".

Does this happen every time?
Yes.

Other information:
See <https://bugzilla.mozilla.org/show_bug.cgi?id=315947> where it has been
suggested (in comment #5) to report a bug here.
Comment 1 Michael Natterer 2012-09-17 21:50:03 UTC
*** Bug 684239 has been marked as a duplicate of this bug. ***
Comment 2 Matthias Clasen 2014-09-16 03:59:37 UTC
not going to change this; just use a utf8 locale
Comment 3 Vincent Lefevre 2014-09-16 07:50:06 UTC
The bug was fixed in fvwm anyway: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339586