Re: [Epydoc-devel] XML Docbook output
Brought to you by:
edloper
From: Edward L. <ed...@gr...> - 2007-02-06 02:01:04
|
On 2/1/07, Saint Germain <sai...@gm...> wrote: >> I know Python, XML Docbook and LaTeX and I'm a heavy user of the >> dblatex project (Docbook to LaTeX, and it's written in Python !) : >> http://dblatex.sourceforge.net >> >> Would you like me to add such a feature and if yes can someone help to >> guide me through Epydoc ? If you haven't already, you should read through the front page of the epydoc API docs: http://epydoc.sourceforge.net/api/ It provides a brief overview of how epydoc is structured. Daniele Varrazzo wrote: > If you want to create a Docbook generator, the best starting point is > largely the LaTeX generator. Agreed. And feel free to suggest changes to the LaTeX generator -- it doesn't get nearly as much use as the HTML generator, and so it isn't as well developed. Daniele's description of how you should go about adding a new docwriter should be enough to get you started, but if you get stuck or have further questions, you can certainly email us. Daniele Varrazzo wrote: > 1. can be cargo-culted from the LaTeX writer, but this probably would > lead to more maintenance burden. Probably a nicer work would be to > refactor the LaTeX writer [...] > > I'd ask Edward if he would welcome the refactoring described in step > 2. I think that creating a Docbook writer the naive way would lead to > harder maintenance, inconsistencies between formats and to too much > code duplication. I think this type of refactoring would be a good idea. I expect the LaTeX and Docbook outputs to be structured very similarly. And there may be other output formats that would also share similar structure. -Edward |