| Newsgroups |
gmane.text.doxygen.devel |
| Organization |
Keristor Systems |
| Message-ID |
<[email protected]> |
On Sun, Mar 02, 2008 at 02:00:35PM +0100, Francesco Montorsi wrote:
> btw if you are not interested to reach 100% well-formness in a single
> patch, then the one I've attached seems to work quite well in terms of
> output rendering (i.e. there are no big differences to the std doxygen
> HTML4, just some spacing differences). I'm not sure however it
> well-behaves respect the other output formats...
It might also break some post-processing some places use. I know
several companies which post-process Doxygen output to create their own
documentation, but I don't know how robust their processing is.
> (*) = I wanted to enable XHTML output in order to use XSLT stylesheets
> over it, instead of doing it over the doxygen XML output.
Have you tried processing it with the W3C 'tidy' program? That usually
does a pretty good job of producing XHTML from HTML with close tags
missing (what lynx calls "tag soup"), and will produce XML as well as
XHTML output. (Doing it on the number of files Doxygen creates is a
pain and slow, though, and you need to disable its comments about how
'bad' the original is.)
Chris C
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/