[PHP-DOC] #30715 [Opn]: Permission Denied mk protocol with chm documents

2004-11-07 Thread john_taylor2 at optusnet dot com dot au
ID: 30715 User updated by: john_taylor2 at optusnet dot com dot au -Reported By: john_taylo2 at optusnet dot com dot au +Reported By: john_taylor2 at optusnet dot com dot au Status: Open Bug Type: Documentation problem Operating System: MS Windows XP

[PHP-DOC] #30715 [NEW]: Permission Denied mk protocol with chm documents

2004-11-07 Thread john_taylo2 at optusnet dot com dot au
From: john_taylo2 at optusnet dot com dot au Operating system: MS Windows XP SP2 PHP version: 5.0.2 PHP Bug Type: Documentation problem Bug description: Permission Denied mk protocol with chm documents Description: I tried to use the php_manual_chm_12.zip file on

Re: [PHP-DOC] TODO

2004-11-07 Thread Sean Coates
Gabor Hojtsy wrote: I am stronly against integrating the HOWTO into the manual content. FWIW, so am I. S

Re[2]: [PHP-DOC] TODO

2004-11-07 Thread techtonik
||*()*|| 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

Re: [PHP-DOC] TODO

2004-11-07 Thread Gabor Hojtsy
I'd like also: - to include HOWTO into docs; GH> What? Do you mean that our end users are interested in the HOWTO? Why? Well, at least to make everything available in one place. If there is a section for PHP extension developers why not to have one for manual writers/translators? For those who alwa

Re[2]: [PHP-DOC] TODO

2004-11-07 Thread techtonik
||*()*|| Hi, Gabor. >> I'd like also: >> - to include HOWTO into docs; GH> What? Do you mean that our end users are interested in the HOWTO? Why? Well, at least to make everything available in one place. If there is a section for PHP extension developers why not to have one for manual writers/tran

Re: [PHP-DOC] TODO

2004-11-07 Thread dirk
- to include HOWTO into docs; What? Do you mean that our end users are interested in the HOWTO? Why? Yes, because most of us started with using PHP before writing (or translating) PHP help. If the information HOWTO is easier available for the end user, properly some more will join us.

Re: [PHP-DOC] TODO

2004-11-07 Thread Gabor Hojtsy
- to include HOWTO into docs; What? Do you mean that our end users are interested in the HOWTO? Why? Yes, because most of us started with using PHP before writing (or translating) PHP help. If the information HOWTO is easier available for the end user, properly some more will join us. More people

Re: [PHP-DOC] TODO

2004-11-07 Thread Gabor Hojtsy
Is it the time to review RFC/ TODO/ lists? It is always time :) I'd like also: - to include HOWTO into docs; What? Do you mean that our end users are interested in the HOWTO? Why? - merge streams section with ZendAPI; Someone needs to find time to look into the ZendAPI stuff deeper, and come up wi

[PHP-DOC] cvs: phpdoc /en/appendices tokens.xml

2004-11-07 Thread Aidan Lister
aidan Sun Nov 7 06:43:22 2004 EDT Modified files: /phpdoc/en/appendices tokens.xml Log: Added some PHP5's http://cvs.php.net/diff.php/phpdoc/en/appendices/tokens.xml?r1=1.16&r2=1.17&ty=u Index: phpdoc/en/appendices/tokens.xml diff -u phpdoc/en/appendice

[PHP-DOC] TODO

2004-11-07 Thread techtonik
||*()*|| phpdoc.. Is it the time to review RFC/ TODO/ lists? I'd like also: - to include HOWTO into docs; - merge streams section with ZendAPI; - describe more functions in PHPAPI; - release a separate PHP3 manual; - think about separate ZendAPI and PHPAPI manual; - ability to link ZendAPI CHM li