Fabien Costantini wrote: > You might be interested to use the doxygen : > \htmlonly and \endhtmlonly pair > (resp. \latexonly and \endlatexonly pair) > to make sure some html (resp. latex) specific tags are only handled in the > html(resp. latex) version.
I considered this too, but then we would have to convert the latex part to UTF-8 anyway, unless we use an image or set the doxygen input character set to ISO-8859-1. And if we convert it to UTF-8, then we can also use this for the html output. But thanks for the hint anyway. 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. (3) use (1) or (2) for FLTK 1.1, and use a combination with \htmlonly etc. for FLTK 1.3, maybe with an image for the latex/pdf version (because scaling wouldn't matter much in this case). Any votes? Mine is (1). Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
