which versions of the manual do we want?

[Francesco Montorsi]

Bryan Petty ha scritto:
> On 3/2/08, Francesco Montorsi <f18m_cpp217828 at yahoo.it> wrote:
>>  The first thing I've tried is to transform through an XSLT the doxygen
>>  XML output into XHTML; however that's going to be a lot of work! doxygen
>>  XML is _very_ much structured and writing an XSLT which produces
>>  something similar to the doxygen HTML output would take a lot of time.
> 
> I was guessing you were going to run into this problem, but I thought
> you might have known something I didn't like having an existing XSLT
> to work off of, but I haven't been able to find one myself.
well, I did the error to think someone else already undertook the effort 
of writing XSLT for doxygen markup doing something similar to what we 
need... unfortunately my researchs and my posts to doxygen mailing lists 
  didn't give any result.


> I've been working on an updated Supybot plugin to read the Doxygen
> XML, and provide reference in the wxWidgets IRC channel to replace the
> existing, outdated wxOracle bot. Lucky for me though, it only needs to
> provide minimal reference information, and I've been fairly successful
> with it so far despite the complicated XML markup that Doxygen
> provides.
good!


> Nothing I've done with this could be used for a stripped down CSS-less
> version of the manual though. It strips out and ignores anything
> complex like code examples and tables, and doesn't even touch any of
> the main pages or overviews.
doxygen XML markup in fact is good for extracting some kind of infos; 
however generating an entire HTML manual from it is another story... I 
should have considered this earlier.


> I do have a different idea that could pan out to a usable CSS-less
> version of the manual. Maybe, given an appropriate LaTeX renderer, we
> can get HTML-only docs from the LaTeX output given with Doxygen. It
> will require that we add another external tool to the tool-chain, but
> won't be just another TeX2RTF solution, heh. I'll take a look and see
> if I can find something we can reasonably use on at least the 3 major
> platforms. It would help if you could do the same in case one of us
> finds something the other doesn't. I'm not too familiar with LaTeX
> parsers, and what's out there.
Ok, I'll do the same. I'm not sure however this is the best solution... 
in the doxygen -> latex -> html conversion I'm not sure of the "quality" 
of the result... it's also true however that the CSS version is not 
going to be the "official" version and a certain "degradation" could be 
acceptable...

Francesco