ini.xml and structure of manual

From: Date: Mon, 16 Sep 2002 21:53:14 +0000
Subject: ini.xml and structure of manual
Groups: php.doc 
Request: Send a blank email to phpdoc+get-969348701@lists.php.net to get a copy of this message
Hi, First: as I can say, the new structure is applied to almost every file (with different success) in the reference part, expect sesam (for details look at reference/rsusi.txt) No glue about this extensions , furthermore it seems to be only in php3 CVS. Therefore it would be kind if someone familiar could apply the new structure and the appropriate ini.xml. Second: As far as my knowledge goes, I added the ini.xml to the extensions in en/reference. Therefore I used scripts/mk_ini_set_table.sh contributed by Jesus M. Castagnetto, thanks!, and a quick look into the current cvs sources. Some questions are still open: Take ncurses/ini.xml as example. ncurses.value"42"PHP_INI_ALL ncurses.string"foobar"PHP_INI_ALL Does this make sense? More ini entries like this exists, e.g. for tokenizer. Apply them, leave them? If someone more experienced could take a look... Third: What about the general, not extension specific, ini entries, like them for e.g. safe mode? Where should they go? To features/safe mode? What about e.g. Error Logging related entries? Will chapters/config.xml exist in the future and in which form? Should all general ini entries(in the above sense) go there? Fourth: About the changelog issues: for ini entries it might be of some interest to add the infos about the availability asap. But how? Maybe someone could enlighen me a bit :-( or provide some suggestions. Regards Friedhelm

« previous php.doc (#969348701) next »