DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2444 Version: 1.3-current Hmm, I see. FLTK has its /own/ implementation of XUtf8LookupString() in src/xutf8/utf8Input.c, and /both/ platforms, SGI and Linux are using it. So the platform specific behavior is not XUtf8LookupString(), but it's in the calls it makes. Seems the problem is with platform specific behavior in: ** XmbLookupString() *** On entry to that function, from what I can tell of the xevent structure, the same data goes in on both platforms, but different data comes back from that function (0x03 vs 0x63). Not sure which is correct. Maybe we need our own version of that function? Or maybe it's a bug long since patched on SGIs. (I haven't patched the sgi in years). Link: http://www.fltk.org/str.php?L2444 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
