Re: [PEAR_PackageFileManager] UserGuide and Tutorial -call for comment
| From: | Martin Jansen | Date: | Mon, 13 Nov 2006 20:14:12 +0000 |
| Subject: | Re: [PEAR_PackageFileManager] UserGuide and Tutorial -call for comment | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-44932@lists.php.net to get a copy of this message | ||
On Mon Nov 13, 2006 at 11:4108AM -0600, Greg Beaver wrote:
> Laurent Laville wrote:
> > For many reasons, as I've already explained in past when I wrote other
> > manuals (in docbook format), this one will be again a standalone
> > version. No pear doc integration.
> >
> > Main reason : I used all dockbook tags I want without restriction and
> > some features that are probably not supported by pear manual architecture.
> >
> > But as, like other manuals I've wrote for HTML_CSS, HTML_Progress2, ...
> > an html copy will be available with next stable release.
> >
> > LAST: I plan to publish the stable release 1.6.0 with a full user guide
> > for November 21st.
> >
> > If someone is not agree or want to see something else in this manual,
> > you have again 9 days.
>
> I can't support this decision. There are hundreds of grammar errors in
> the documentation you've written, and more than one factual error.
I think we can sort of live with the grammar errors and a lot of people
can easily fix them. (If we get that thing into CVS *grin*.) But it
would be good if you told details about the factual error (unless
Laurent already knows about it), because most people won't likely notice
that one.
> I don't see any good reason to avoid the PEAR manual. The thing is
> already in docbook! It wouldn't take long to tweak it to fix any
> compatibility issues encountered. Most important, it cannot be
> translated or edited by anyone else as long as it it outside of CVS.
Laurent, if you need help in merging the documentation into the manual,
just drop a note. It would be sad to see this fail because of technical
reasons.
- Martin