>     Sorry, I missed that this was input related.
>     (My comments were regarding utf8 display only)

No, my original question/proposal wasn't specifically input related,
but I have to admit that I hadn't actually thought about it either.

I thought it would be useful to poll the users to see how many
people are looking for which level of support. If there is only
a very small number who need support for the most complex level,
then we shouldn't delay 1.3.0 trying to cater for them.

So maybe the poll should have paired questions for the more complex
levels, asking whether they require display only, or input as well.

Clearly we can already handle display and input of plain ASCII,
and Western European Accented characters, so maybe 1.3.0 should
aim for right-to-left simple character sets (Greek, Cyrillic...),
and 1.3.1 should aim for "right-to-left" complex sets (CJK) and
later releases look at "left-to-right", "top-to-bottom" and more
complicated issues if needed.

Matt's idea of re-labelling parameters with a utf8 [prefix?] is
a good one, and would aid solving http://www.fltk.org/str.php?L1903
Deciding which of the utf8 related functions that are documented
in the "Unicode and UTF-8 Support" of the 1.3.x User Manual would
be the first step.

Then we should prioritize the UTF-8 related STRs as to whether they
go in 1.3.0, 1.3.1 etc as determined by the poll results perhaps.

The highest priority STRs for UTF-8 at the moment mostly relate
to CJK display and input, and these are clearly blocking release
of 1.3.0. If we can move those into a later release, we should be
able to get a 1.3.0 out sooner rather than later, and that should
raise confidence in the user community, no?

And as someone else suggested, maybe we can duck the issue of input
for complex composed character sets by using the native OS features
or external libaries, but we can put that on the back burner for now.

Cheers
D.

PS. Having stirred the waters, I hope to have time for fltk soon :-)


_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to