Here's a bunch of thoughts and questions around PEAR and PHP 4.1. Any
input is much appreciated.
On php-dev we're trying to get together a plan for PHP 4.1 now. One
of the things we want to do is to take most extensions out of the PHP
distribution itself and make them available for example though PEAR.
That touches upon the problem of merging documentation from PEAR
(there actually is some, hidden in JavaDoc comments :-)...
When PEAR and PHPDoc finally get to the point where you can easily
generate DocBook reference docs, how should we deal with that?
Should all the PEAR docs become part of the manual? Maybe only the
PEAR packages bundled with PHP should be part of the manual? If so,
how do we best make the rest of the PEAR docs available?
The PHP manual is kinda suffering from the same problem as PHP itself:
it's huge.
Is it worthwhile to try doing something about that, by splitting the
manual up somehow?
Can we do a clean modularizing within the DocBook framework?
What difficulties could splitting cause to translations?
- Stig
--
Stig Sæther Bakken <[EMAIL PROTECTED]>
Fast Search & Transfer ASA, Trondheim, Norway
