Re: future of PEAR
| From: | Jon Parise | Date: | Wed, 12 Nov 2003 00:26:49 +0000 |
| Subject: | Re: future of PEAR | ||
| References: | 1 2 | Groups: | php.pear.dev php.pear.doc |
| Request: | Send a blank email to pear-dev+get-23487@lists.php.net to get a copy of this message | ||
On Wed, Nov 12, 2003 at 12:20:41AM +0100, Stefan Neufeind wrote:
> Just a while ago I read an article in the German Linux Magazine about
> editing docbook using OpenOffice. Wouldn't that be a point that could
> be followed further? Like, writing a doc for everybody how to use
> common and freely available tools like OpenOffice to write docs? So
> wouldn't following the way of docbook be a good idea since it's a
> settled standard for writing docs - although hard to do without
> appropriate tools, agreed.
While I think it's great that OpenOffice can handle DocBook, I have
two problems with this approach (for PEAR):
1. OpenOffice is big, and it seems like a waste of developer
resources to require it in order to write documentation for a PEAR
package.
2. OpenOffice assumes a GUI-based environment.
Granted, those developers that take issue with either of these (such
as myself) are free to edit the Docbook source in a standard text
editor, unless PEAR requires some sort of OpenOffice-specific
templates or something.
My other main problem with Docbook is, once you've figured out how to
edit the XML-based source code, you need to install a chain of
rendering tools (i.e Jade) before you can see any formatted output.
--
Jon Parise (jon@php.net) :: The PHP Project (http://www.php.net/)