Re: Re: API presentation vs API atoms description. Was:

From: Date: Sat, 18 Dec 2004 05:29:47 +0000
Subject: Re: Re: API presentation vs API atoms description. Was:
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15  Groups: php.pear.qa 
Request: Send a blank email to pear-qa+get-2226@lists.php.net to get a copy of this message
with docbook, this is completely impossible without learning an archaic dsssl language that nobody seems to be able to read. It's like the old medieval Catholic masses where the priests spoke in Latin and nobody had any idea what they were saying :).
Docbook layout can also be managed using XSL (not in the current peardoc afaik) and there is livedocs which gives more flexibility.
Yeah, but writing a successful xsl for docbook is a full-time 3 month job that makes me shudder even thinking about it :)
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. 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. Sorry if this is getting offtopic. It just hurts to hear docbook dismissed so readily amongst the PEAR folk. (-; S

« previous php.pear.qa (#2226) next »