Character composition remains necessary even with support of localized keyboards. For instance, French keyboards can produce ç (c with cedilla) but need character composition to produce ü (u with umlaut). Thus, I believe we should not eliminate composition altogether.
What has been done in Mac OS X is to use the system's character composition support instead of FLTK-defined composition rules. The perfect solution would be to do the same under WIN32 and X11. > Do we want to keep this feature or eliminate it? > > Please vote! > > > In FLTK, pressing the right Ctrl key in combination with two more = > keystroke will (should - it seems to be broken) combine those two = > keyboard characters in a more or less meaningful way. > > For example, Ctrl+A+" could produce =C4 (A-Umlaut), etc. . This seems to = > be broken now that we use UTF8.=20 > > The compose key is a remainder from the times where international = > support was rare on Unix and German keyboards were not available on SGI = > (yes, that's how old that is ;-) > > I wonder if we should keep composing around at all. Todays X11 clients = > are well aware of international keyboards, so entering whatever local = > character should be easily done without FLTK interfering with user = > settings. > > BTW, we threw all the FLTK composition stuff overboard on OS X already = > (their laptops have no right Ctrl key to begin with). Maybe it's time to = > do that on Unix and MSWindows as well?! > > - Matthias= >
_______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
