Recommendations for Docbook XML transformation with Python?

[Phil Frost]

I have success in getting libxslt to work, although it was something
less than a nice experience. Setup wasn't a problem, but the docs we
scant and the interface is less than pythonic.

There are some other XSLT interfaces listed at
<http://pyxml.sourceforge.net/topics/software.html> that might be
better.  I haven't tried any of them.

If you havn't already waded through all the ETLAs to understand how XML
DocBook is usually transformed into other formats, the process is
generally to use an XSLT processor to transform the DocBook into HTML,
or XSL-FO, which is an XML language that is the complement to DocBook,
describing only formatting. From there, I have read there are tools that
can generate RTF, PDF, etc, but I've never used any of them; I've only
generated HTML. The usual XSLT distribution is at
<http://docbook.sourceforge.net/projects/xsl/>.

Good luck!

On Sat, Jul 24, 2004 at 08:53:22AM +1000, Tim Churches wrote:
> These days, what is the best way to transform DocBook XML into HTML,
> RTF, PDF and other targets using Python? Googling around the topic
> throws up a bewildering array of acronyms, but it seem that using
> libxml2, libxslt and the libxml2-python bindings might be the best way
> forward??? The latest versions of libxml2 and libxslt compiled without
> problems (on a RH Linux 8 machine), but setup (compilation and
> installation) of the latest libxml2-python binding fails (with Python
> 2.3.3). Should I persist, or is there a better direction to take? 
> -- 
> 
> Tim C
> 
> PGP/GnuPG Key 1024D/EAF993D0 available from keyservers everywhere
> or at http://members.optushome.com.au/tchur/pubkey.asc
> Key fingerprint = 8C22 BF76 33BA B3B5 1D5B  EB37 7891 46A9 EAF9 93D0