Python documentation in DocBook
Martin v. Loewis
martin at v.loewis.de
Wed Nov 13 16:16:27 EST 2002
DaveP <DaveP at NEARLYdpawson.freeserve.co.uk> writes:
> > - there must be tools to process the resulting XML, such tools are
> > currently not available. We would require HTML, Latex, and texinfo
> > output, perhaps Windows CHM (whatever that is) as well. No such
> > tools are available at the moment.
>
> I believe this to be wrong.
> HTML, PS (guessing that's why you want Latex?) Windows help and PDF
> are all available for docbook.
Yes, it is possible to produce HTML and PS. No, it is not possible to
generate the HTML and PS that we want. I can generate HTML from
/vmlinuz, by means of
print "<html><body></body></html>"
but that doesn't make the HTML generation useful.
> Did you have the same trouble moving from plain text to \latex?
That was never necessary: Python documentation was LaTeX from start
(AFAIR - I think it was FrameMaker at some point, and was converted to
LaTeX - but that was before I contributed to it; FrameMaker would be
fine for me as well).
> Just curious why you aren't using quills/biro's.
Never heard of either quills or biros (ok, it's just not in my
vocabulary).
Regards,
Martin
More information about the Python-list
mailing list