On 26.10.2010, at 22:08, Albrecht Schlosser wrote: > Matt wrote: > >> I would like to suggest a mode of action to get UTF8 support complete. >> My main issue is not knowing where to start and which places in the >> source code were already touched. We agreed a long time ago to not >> introduce a new string type, so here is what we could do: >> >> Any parameter that should take a text string should contain utf8 in its >> name. For example, once we change >> >> Fl_Widget(int x, int y, int w, int h, const char *label) >> >> and *all* functions that depend on it, we can change the footprint to >> >> Fl_Widget(int x, int y, int w, int h, const char *label_utf8) > > I don't think that this is very useful. *ALL* strings in FLTK 1.3 must be > UTF-8 encoded.
I only meant to use this to mark functions which we verified that the *do* work with utf8. This is only a developer crutch. I'll come up with something different. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
