> Correction: For FLTK 1.1 we can probably only use the html
> entity encoding,
> because htmldoc (documentation/make fltk.pdf) doesn't
> understand UTF-8, but it
> _does_ understand the html encodings ("&xxx;"). I tested only
> a few, but
> according to the code, there's a table that contains all the
> needed ISO-8859-1
> character encodings.
>
> Or is there an option that we can set for htmldoc? Does anybody know?
I guess Mike would know...!
I'm veering towards thinking that putting the html encodings in the text
is the way to go, it will be "safe" under editors that don't grok UTF-8
and so forth and ought to render correctly on all modern browsers.
But I don't have any useful idea what to do about doxygen then...
On a completely unrelated note, Fabien (if you are around) did you get a
chance to look at the STR #2242 at all?
It has a patch for using "fltk fonts" with the cairo context, in which I
think you are the expert... Is this any good?
Cheers,
--
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
