I would like to use Sphinx to produce the documentation for coverage.py. I like the idea of the sources for the docs being ReST files, and using autodoc to pull in module documentation. But the final results will be published on my website, which uses a custom XML-to-HTML generation tool. I'd like Sphinx to output the XML that will be the input files for my custom process. The XML is just simple HTML (p, ul, li, em, a tags, etc.) with page-level information as well, in files named *.px. So I'd use Sphinx to convert .rst to .px, then my tool to convert .px to .html.
I started down the path of tweaking the existing HTML translator and builder, but it gets very complicated, and I keep running into gaps in the docs (how do I register a new builder?). It seems like there should be a straightforward way to accomplish what I want, but I can't see the forest for the trees. What would you recommend I do? --Ned. -- Ned Batchelder, http://nedbatchelder.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
