Albrecht Schlosser wrote:
> For me this looks now, as if the path of least resistance would be:
>
> (1) convert the table to UTF-8 and add a charset statement to the FLTK
> 1.1 docs, where appropriate - with the drawback I mentioned before, that
> we would have more UTF-8 encodings in the FLTK 1.3 source and header
> files. This way we would be able to keep the same table for both.
>
> (2) second-best option: use the html entity encoding (&xxx;) for FLTK
> 1.1, but UTF-8 for FLTK 1.3.
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?
Albrecht
_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev
