||*()*|| Hi, Gabor. GH> more parts). Now what is better, having all the stuff at one place, or GH> three manuals (PHP Users Manual, PHP Developers Manual, PHP GH> Documentation Howto). IMHO three documents are better. They only need to GH> have three root XML files, and their files can reside in the same CVS GH> module, as it is now. We already have a root file to generate the GH> install part only. I am stronly against integrating the HOWTO into the GH> manual content. Well, you've convinced me. =) Three are better than the bloated one. But we can think about one additional manual "all-in-one", which will include all three parts and perhaps PECL and PEAR stuff.
>>>>- think about separate ZendAPI and PHPAPI manual; >> >> GH> What do you mean with PHPAPI here? >> Well, you are right. It's a mistake. PHP Manual. Merge Streams and >> PHPAPI sections into ZendAPI and release a separate developers manual. >> So PHP users can search only PHP manual and developers can use their >> own. GH> So then why to integrate the HOWTO, I don't see the consistency. Agreed. General information about translating activities and developing manual with links to docweb and HOWTO is enough for most cases. t --
