All due respect, but the (x)CHM for phpdoc uses XSL, much of that can/should be re-usable.
The POINT of Docbook is portability.
Also, once I get my peardoc karma, I'll hopefully be taking a look at peardoc and livedocs. There's no reason that PEARDOC couldn't use livedocs for display on pear-web, once this is working.
I don't think anybody took the necessary time tp play with livedocs and peardoc until now :)
Docbook is not [entirely (-;] magic. It's XML. It can be processed using any XML processing method, including but not limited to DSSL, XSL, simplexml, regex, etc. Of course the best way to do this is with one of the methods that's designed to process xml into another output format (XSL, DSSL).
Additionally, take a look at the docweb project. We could use more eyes/hands. The goal is to consolidate the various doc projects under one roof.
I've been following it since the beginning but time being an issue I haven't participated much yet.
Sorry if this is getting offtopic. It just hurts to hear docbook dismissed so readily amongst the PEAR folk. (-;
It's not docbook, with the proper skeleton it is pretty easy to get started. The problem is seeing the result, the build environment is not easy to setup and having to rebuild the entire manual for a single char change is really annoying.
This is where livedocs should help, if somebody can commit and see the results right away it should help a lot.
That being said the wiki is still planned :)
Arnaud.