Greg Ercolano wrote:
>>> On 24.10.2010, at 16:33, Duncan Gibson wrote:
>>>> 5. complex character sets (Chinese, Japanese, Korean...)
>
> Manolo Gouy wrote:
>> As for level 5, we need a developer who's a user of CJK. Without,
>> there's little hope to achieve this goal. Do we have that ?
>
> 1.3.x already does complex character sets Chinese, Japanese, Korean...
Sorry, I missed that this was input related.
(My comments were regarding utf8 display only)
I see now you probably mean keyboard entry of non-western characters
(ie. typing CJK characters into input fields, where little "assistant
widgets"
pop up to help the user type these characters).
I haven't ever needed non-western input capabilities, so my apps
are not a good example for that.
I understand CJK input is a tough issue, because native OS's have
their own little way of popping up per-character menus that assist
the user with CJK input, including some clever predictive techniques,
similar to e.g. iphone's real time spell checking bubbles that popup
while typing words.
I suppose this is where FLTK would either need to rely on an external lib,
or somehow allow the native os to "take over" keyboard data entry enough
to be able to popup its native widgets within the FLTK app (similar to what
Fl_Native_File_Chooser does). I know zippo about CJK input, but understand
it might be a complex issue.
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
