MacArthur, Ian (SELEX GALILEO, UK) schrieb: >> The fastest solution would be to change INPUT_ENCODING to ISO-8859-1 >> (and I'm not keen on having UTF-8 characters in my non-UTF-8-aware >> editor (nedit) as well), but I remember that Matt added some >> UTF-8 text >> to some source file(s). However, I don't remember which one, >> and if this >> was for documentation or comments only. >> >> Other opinions? > > An option might be to generate a gif or png of what the table should > look like and use that, thereby dodging all font or transliteration > issues on any target machine, and independent of charset. > > Is that any good?
Sounds really good. Maybe not suitable for all similar issues, but for the character composition table this would be a *good* solution. One drawback however, as always with images that contain text: they are not as well scalable as the original text in a browser, but I think that this can be solved appropriately. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
