DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR Pending] Link: http://www.fltk.org/str.php?L2416 Version: 1.3-current I did some investigations, too, but didn't find a solution. However, I found that 'xprop' is a good tool to show X window attributes. It shows that some programs use COMPOUND_TEXT for setting the UTF-8 window name, for instance (nedit): $ xprop|grep NAME WM_LOCALE_NAME(STRING) = "de_DE.UTF-8" WM_ICON_NAME(STRING) = "x.tmp" WM_NAME(COMPOUND_TEXT) = "x.tmp - /.../fltk-1.3/äöüÃâ¬/" note: xwininfo -name "..." doesn't work. Similar test for a fltk-2 editor (file "äâ¬.txt"): $ xprop | grep -i name WM_ICON_NAME(STRING) = "äâ\302\202¬.txt" _NET_WM_ICON_NAME(UTF8_STRING) = 0xc3, 0xa4, 0xe2, 0x82, 0xac, 0x2e, 0x74, 0x78, 0x74 WM_NAME(STRING) = "äâ\302\202¬.txt" _NET_WM_NAME(UTF8_STRING) = 0xc3, 0xa4, 0xe2, 0x82, 0xac, 0x2e, 0x74, 0x78, 0x74 -> xwininfo -name "äâ¬.txt" works. Looks as if Greg's (fltk-2's) solution is maybe the best? P.S. I don't know if all these UTF-8 characters make it to the STR page, but I tried it at least to provide some more info. Link: http://www.fltk.org/str.php?L2416 Version: 1.3-current
_______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
