> > > In r. 8569, Fl_Quartz_Graphics_Driver::width(unsigned int wc) > > is modified to handle properly wc > 0xFFFF. > > > Yes - see that. > Do we need to think about adding a one glyph UCS->UTF16 function? > I mean, rather than calling fl_utf8encode() then fl_utf8toUtf16() to do > the job. > > It would probably make your patch simpler and also might help with the > win32 width() mods, too.
I believe Fl_Quartz_Graphics_Driver::width(unsigned int wc) is very seldom used because in most situations, one has to measure a string and not a single character. In FLTK, it's used only in Fl_Help_View to measure the space character. If conversion from a single UTF32 character to UTF16 is useful for Fl_GDI_Graphics_Driver::width(const char* c, int n), a new function could be useful. But if it's used only in Fl_GDI_Graphics_Driver::width(unsigned int wc), I don't think it's justified. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
