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 Regarding COMPOUND_TEXT vs. UTF8_STRING, definitely others have been where we are now before (googled for those two words): Discussions: http://www.gnu.org/software/emacs/manual/html_node/emacs/Communication-Coding.html http://www.spinics.net/lists/xorg/msg03466.html http://lists.x.org/archives/xorg/2004-September/003444.html http://lists.freedesktop.org/archives/xdg/2004-September/003331.html Here's a description of COMPOUND_TEXT as iso-2022 (ie. 8 and 16 bit encodings of text) http://mail.gnome.org/archives/wm-spec-list/1999-July/msg00110.html http://en.wikipedia.org/wiki/ISO/IEC_2022 I think this is the email thread that started the whole _NET_WM_NAME thing being added to the window manager spec: http://mail.gnome.org/archives/wm-spec-list/1999-July/msg00106.html My take on COMPOUND_TEXT (keep in mind I'm not much familiar with this stuff) is that if FLTK's mission is to only support UTF8 encoding, then we should probably only use UTF8_STRING with the window manager. I think COMPOUND_TEXT is for (or includes) other encodings we don't support, and was only used for old window managers that didn't yet support UTF8 which are probably waning fast. 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
