Hi Goba!
I have already started documenting the Unicode stuff about one year ago
(http://php.net/unicode). Most is already out-of-date, but it is a start
point.
What we were discussing is if we should change every page to mention that it
is unicode-safe/aware/compatible/whatever. We were all against that because
changing every single file would be a pain for us and mainly for the
translators. All functions will be converted by the time PHP 6 is released,
so there is no really interest in marking every single function as such.
What we can do (and should) is to add some information to the reference.xml
file about how the extension handles unicode data (for example, the xml
extensions use utf8 internally because of libxml, etc..)
Nuno
Our policy was always to document functionality when people have time and
willingness to do so, even for funtionality available in stable versions
in the future. The new Unicode stuff needs to be marked as such, but IMHO
has its place in the documentation. People need to see that there is a
light regarding Unicode!
Gabor
On Wed, 19 Jul 2006, Andrei Zmievski wrote:
I think this information could be useful since people will most likely
want to use online manual even before PHP 6.0 final is out. Making them
go to a separate site to look up which function is Unicode-safe or not is
not very user-friendly.
-Andrei
Since all appropriate functions will be unicode compatible in PHP 6.0.0
this seems like information overload and not something that should be
mentioned in every functions documentation. Perhaps have a list offsite,
maybe on docweb, for alpha/beta testers.
