Ah yes, this makes sense and his last post did clarify that (hindsight is 20/20!). Sounds like a good idea to document all these types of changes so to the original question on when: ASAP! :-)
Yes, that's a good idea. :) Most of the functionality in the core language will not be changing so the documentation effort can start immediately. I would offer to document some things myself, but honestly, I think that my time is best spent finishing up core stuff, doing Unicode upgrades of core functions, and nagging other developers to upgrade their extensions. But I'm perfectly willing to provide answer about Unicode features to those who wish to start this documentation effort.
Perhaps you could provide an example or two on "how to document a unicode change" as currently I for one would not know where to begin. Like the best way to go about finding [1] and documenting a unicode related change. And an estimate on about how many functions will eventually require documentation changes for this. 50, 200, 500, 1000, ...?
One note: The PHP documentation is in the middle of being converted to a new doc style [2] that includes individual Changelogs so ideally the document would first be converted to this new style (about 30% of the manual is currently), and then this change would be done. Ideally...
Also, the doc team is sort of on vacation currently but once Livedocs [3] is online I have a feeling we'll make a concerted effort to attract additional help on all fronts.
Regards, Philip [1] http://www.php.net/~scoates/unicode/ [2] http://wiki.phpdoc.info/DocSkel [3] http://livedocs.roshambo.org/
