> what would you recommend to check for utf-8 enabled FLTK. The > fltk-config script does not give any hint.
With the utf-enabled build, the config script is now called "fltk-utf8-config" - if you invoke "fltk-config" you should be getting the non-UTF8 fltk. > As well a check for utf-8 would be nice to have at runtime. I'm not sure I understand? What would we check for? All the o/s we support are capable of doing UTF8 these days, and there is no robust way other than explicity testing, to ascertain (except maybe on a Mac) whether a given font has the glyphs you need or not... > One fragile possibility could be to tell Fl::version() to put out > 1.010850 instead of 1.010800 > But not shure if this is relyable through all the FLTK > versions around. For now, I'd strongly favour static linking... Until we get all the issues resolved. Always remember that the low-level binary API is different between the regular fltk builds and the UTF-enabled fltk builds, so code built to use the UTF8-fltk CAN NOT be used with the regular-fltk shared objects (or DLL's or dylibs) since they have different sizes for a lot of key parameters. If you have code compiled for the UTF-fltk linking at runtime to regular-fltk shared objects (or vice versa), then chaos will surely follow... > Currently I check statically for the _Xutf8_h macro after including > <FL/x.H>. But this seems not stable, as you indicated to > remove or merge some files. Yes, I have started on that, but (for X) Xutf8.h will probably continue to exist. I'm not sure. Might be better to check for fl_utf8.H as that should exist in all platforms, and will not go away... Probably... SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
