cvs: phpdoc / TODO

From: Date: Fri, 18 Jan 2002 15:22:28 +0000
Subject: cvs: phpdoc / TODO
Groups: php.doc 
Request: Send a blank email to phpdoc+get-969341383@lists.php.net to get a copy of this message
hholzgra Fri Jan 18 10:22:28 2002 EDT Modified files: /phpdoc TODO Log: some additions Index: phpdoc/TODO diff -u phpdoc/TODO:1.20 phpdoc/TODO:1.21 --- phpdoc/TODO:1.20 Tue Jan 15 06:28:51 2002 +++ phpdoc/TODO Fri Jan 18 10:22:28 2002 @@ -10,7 +10,12 @@ - licensing issues, possible licenses - users manual / developers manual division? effects on folders, files, make system, style sheets - + - have seperate cvs modules for translations + as most of us need only one or two languages + - split files down to function level? + (see also BUILD SYSTEM: translation detection) + - category support for the reference part + (see also BUILD SYSTEM: group and organize functions logically) IMPORTANT: - connection handling: what about, what got nuked? @@ -31,7 +36,6 @@ - add DTD - convert funcsynopsis to methodsynopsis (using scripts/process.php) - change configure/make - - put translations in seperate cvs modules? (to be discussed) - translation detection on function level (hartmut) - easy way -> split reference files down to function level and keep current file-based detection mechanism @@ -50,7 +54,10 @@ huge files to manageable pieces - get back lost indexes, but add them as appendixes (index of tables, index of examples) - + - make configure generate entities for the new file structure + of the ZendAPI stuff (hartmut) + - merge back build system/style sheet improvements from + phpGtk and pear manual (hartmut) GENERAL: - Document php://stdout etc feature for file functions.

« previous php.doc (#969341383) next »