Python documentation in DocBook

[Martin v. Loewis]

Peter Hansen <peter at engcorp.com> writes:

> At least one I can think of is that if the source were in XML, 
> something I can manipulate with my eyes closed thanks both to
> its simplicity and to the herculean efforts of the many people
> who have contributed to the many Python XML technologies, I 
> would have the opportunity to "play" with it, and quite possibly
> would come up with some novel things to do with it that those
> who currently have access have not, and perhaps would not, have
> thought of.

That is, unfortunately, not a convincing-enough reason: the
possibility that somebody may find a use for the documentation that he
can't think of right now.

In any case, if you really want to look at it, there is a tool chain
that converts the existing documentation to XML for you to ponder.

> Is my description of a potential good, "however slight" it may
> be, sufficient for you to concur there just might be some benefit.
> I could come up with stronger arguments, I believe, but that
> doesn't seem worthwhile at this point in the discussion.

Most likely. It appears that your potential uses would all deal with
new processing opportunities, in which case I would always refer to
the existing conversion to XML, which then could be used as a starting
point for whatever new processing strategies people come up with.

For this kind of application, it is not necessary that the primary
source is XML; it is sufficient that XML can be derived from it.

Regards,
Martin