2009/7/9 Thomas Adam <[email protected]>: > 2009/7/9 Manoj Srivastava <[email protected]>: >> Hi, >> >> This was reported by a Debian user. Please retain >> [email protected] in your responses, so that the Debian >> BTS may have a copy of your response. >> >> ICCCM specifies WM_NAME, as an uninterpreted string, in the >> latin-1 domain, I think, EWMH specifies _NET_WM_NAME as utf-8; also >> Note that freedesktop.org WM spec already defines >> _NET_WM_ICON_NAME >> _NET_WM_NAME >> both of type UTF8_STRING, to be used in preference to WM_ICON_NAME and >> WM_NAME. (http://freedesktop.org/Standards/wm-spec/1.3/ar01s05.html >> and http://standards.freedesktop.org/wm-spec/wm-spec-1.3.html#id2506989) > > But _NET_WM_NAME is used via ewmh_name.c:EWMH_WMName() -- this gets > called from add_window.c:setup_window_name(). > > The EWMH_WMName() function uses FiconvUtf8ToCharset() which is our own > wrapper around iconv to convert the given UTF8 string to the current > charset the system is set to -- be it Latin-1 or indeed UTF8. > > Has this been verified with FVWM 2.5.28 (CVS, basically)? The test > case works fine here: > > [n6ta...@shuttle][~]% xprop -id 0x4200008 | grep NET_WM_NAME | \ > perl -ne 'while (/(0x[0-9a-f]{2})/g) { printf "%c", hex $1 }' > urxvt%
Oh -- and I ought to mention, the application itself has to understand UTF8 since it sets the _NET_WM_NAME XAtom in the first place. You can do this for yourself (I assume you're running under a UTF8 locale, etc., already): 1. Start up xterm. 2. unset PROMPT_COMMAND 3. printf \\033]0\;\%s\\007 "Hello: ßßß" 4. xprop -id $WINDOWID | grep _NET_WM_NAME (will show nothing,) 5. CTRL-right-click on the XTerm window and select "UTF8 titles" 6. Repeat step 3. 7. Repeat step 4. 8. _NET_WM_NAME(UTF8_STRING) = 0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x3a, 0x20, 0x20, 0xc3, 0x9f, 0xc3, 0x9f, 0xc3, 0x9f And you'll see "Hello: ßßß" -- with three German "ss" symbols. If this isn't even close to what you're describing, or you have something completely different, then do say, and where possibly provide steps on how to reproduce your problem, and/or provide a sample FVWM configuration. -- Thomas Adam
