cvs: phpdoc /RFC protocol_20020310

hholzgra Tue Jun 11 06:35:57 2002 EDT Modified files: /phpdoc/RFC protocol_20020310 Log: added some progress comments Index: phpdoc/RFC/protocol_20020310 diff -u phpdoc/RFC/protocol_20020310:1.1 phpdoc/RFC/protocol_20020310:1.2 --- phpdoc/RFC/protocol_20020310:1.1 Wed Mar 13 04:57:58 2002 +++ phpdoc/RFC/protocol_20020310 Tue Jun 11 06:35:56 2002 @@ -24,6 +24,8 @@ on PHP documentation has PHP installed, so this new requirement should be easy to meet ;) +9.6.2002: finished (hartmut) + 2. File split We like to propose to split up the XML files in the phpdoc/functions subdirectory into an introduction part and seperate small files for @@ -47,6 +49,15 @@ allow for local entities files for extensions in the future, making the transition of documentation for extensions that get moved to PEAR/PECL easier. +9.6.2002: finished (hartmut) + works fine now, just our (my?) assumption about CVS scaleability + were totally wrong ... we've now created aliases allowing to + check out the english version only or combined with exactly + one translation, as this is what the usual author or translator + needs (we discussed this during the meeting, but somehow this + topic didn't make it into the protocol) + + 3. Zend API doc integration The ZendAPI documentation is not yet well integrated into the manual. It should at least be an appendix instead of a regular @@ -130,6 +141,8 @@ DocBook->TeXinfo->man should be considered instead of the current fix (PS: seems like derick has fixed the script for now, but it will most likely break again when the file split is done while an XSLT solution would not ...) + +9.6.2002: now working even with splitted files (hartmut) 9. CHM for non-Windows environments We'd like to have access to the CHMs created by goba on Linux (and