[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [patch] python docstring generation with swig through doxygen

From: Max Bowsher <maxb_at_ukf.net>
Date: 2005-03-31 13:05:18 CEST

Leo Simons wrote:
>> Hi gang!
>> Please CC me on replies as I'm not subscribed to this list.
>> I'm not sure if you've seen it yet, but someone has written a script
>> doxy2swig.py [1] that takes a doxygen-generated xml file and transforms
>> it into a swig interface file that contains docstring declarations for
>> python [2].

Definitely interesting.

>> I had a go at running this over the subversion codebase. The attached
>> patch fixes all "&" used in comments to be "&amp;", so that the xml
>> doxygen generates is actually valid xml and the subsequent parsing
>> stages can succeed (which might be a good idea to apply anyway...). It
>> then also modifies doxygen.conf to actually output xml...


First, there's no point doxygenifying comments which are not processed by
doxygen - so that means, nothing outside subversion/include/.

Second, doxygen (I'm using 1.4.2) appears to be automagically entity-fying
the & characters in the HTML output engine (but not very consistently).

If I apply your patch, I get a link like:

<a href="....&amp;.....">......&amp;amp;........</a>

which is clearly wrong.

So, since the HTML is the primary output format for us, I must reject this

Perhaps you would like to contact the doxygen people, and report this
inconsistency between the HTML and XML output engines?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 31 13:06:55 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.