> > On 24.10.2010, at 16:33, Duncan Gibson wrote: > > > Can we split UTF-8 support down into slices, and aim for those? > > To see whether this even makes sense, I would propose having a new > > poll question along the lines of: > >=20 > > What level of character support do you require from FLTK in the = > future? > > 1. plain ASCII only, so UTF-8 support needed > > 2. ASCII plus Western accented characters > > 3. simple left-to-right character sets (Greek, Cyrillic...) > > 4. simple right-to-left character sets (Arabic, Hebrew...) > > 5. complex character sets (Chinese, Japanese, Korean...) > > We are beyond 1. and 2. already. 3. is the minimum we must do in UTF8, > but 4. should be the goal IMHO. I don't know enough to ever solve 5. as = > a whole. > > > - Matthias >
Haven't we already reached level 3 as well? I doubt level 4 can be reached because arabic requires complex, context-dependant, processing that is done natively by MSWindows and Mac OS X but requires large external libraries under unix/X11 (e.g., Pango). 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 ? _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
