> Using fltk-1.3, on linux and win32 systems, when I want to input > Japanese or Chinese text, for example, I invoke the host system's IME > and enter text in that. > The IME then sends the composed UTF8 sequences to the foreground > (fltk) window and all seems to be well. > > Fltk's own, historical, compose key mechanism does not seem to me to > be involved (indeed I suspect that mainly handles the typing of LGC > glyphs that don't appear on a your keyboard, e.g. me typing ß on a UK > keyboard that has no key for it...)
Hmm, well if that's true, isn't it all redundant and can be removed right now? Even if it does provide some feature beyond the system's like the ability to type some glyphs without switching IME, no one is going to know how to use it because no other app on the system does that. > I am not familiar with the Apple IME, so don't know if that works - I > assume that it does, though? Or are you saying that it does not? It doesn't for me... >> In fact, it might be nice to completely replace the text input widgets >> and get standard editing commands in the bargain (I'm always surprised >> when command-a doesn't select all). > > Hmm, CMD-A seems to work for me on this Mac (just tried a few simple > widgets though.) Where is it failing for you? The part where everything gets selected :) I'm on OS X 10.5.8 and I just tried with test/input on the latest 1.3. Cmd-a does nothing. Perhaps the issue with selection is the edit menu, normally cmd-a invokes a command on the edit menu, but fltk apps don't have Edit by default. I guess that's logical enough. Since mac apps all have a standardized edit menu, maybe there could be a statically defined edit menu that you could put in Fl_Sys_Menu_Bar? Zhuyin input enters the zhuyin characters but they never build into proper characters. Normally when you hit a tone mark, a choice window pops up, and after picking the right character it replaces the zhuyin cluster. Similarly, pinyin writes latin characters until you hit space, at which point you get the character choice menu. The windows IMEs are basically the same but I haven't tested them on fltk. However, on fltk the character build window never comes up, once again using test/input. You can test yourself easily enough, just go to prefs -> international -> input menu and enable "Traditional Chinese" and pinyin + zhuyin (for some reason it insists at least two be enabled), select pinyin from the input menu and then type budui<space> in any app and see what happens. I tried with arabic and it seems to work normally (though I don't know the language so I'm not sure :), even the right to left part. Japanese input has the same problem as Chinese. So it looks like the input methods that do character replacement don't work. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
