> 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? -- Ian 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
