> In an IRC chat with Derrick, it was brought up that getting translators to > work with CVS branches could possibly make my idea undoable (i.e., it's > asking too much of people to learn how to use branches properly). > Personally, I disagree, but that can be discussed here as well.
An itelligent web frontend for doc editing [which we talked about already] would solve all problems. This way anyone would be able to add docs, and some translators would be able to approve the changes sent in from the web... > The Changelog idea would be an excellent addition to the docs. You'd need > to figure out how to handle functions that get dropped (like xmlfile(), for > instance). I suppose that could go in the Changelog for the main DOMXML > introduction page (but then would there be any docs for obsolete > functions?). Obsolote function can be left in the doctree now. We can build a small script extension to the extension function list generator to group the obsolote functions to another group, not to the main list. Now all the functions are in different files, so you only need to define a mark for obsolote functions. > And incorporating something like http://www.zend.com/phpfunc/ into the PHP > docs would be a big benefit, I think. Hrmm ... it even looks like it > handles obsoleted functions. This is already incorporated. The function compatibility data is generated from that table. You cannot get much more from there for a function AFAIK... Or am I mistaken? I do not use phpfunc too often... Goba
