I'm unsure if I follow what you mean here Gabor, please clarify.
If we do this soon then later we'll undo it all because when PHP
6.0.0 is released every [appropriate] function will be unicode
compatible so repeating this thousands of times throughout the
manual won't be useful. The appropriate place to document "the
progress" of unicode support for pre PHP 6 should not be in all these
manual pages as we do not document alpha/beta releases. If for some
reason a function is missed and support is given in, for example, PHP
6.0.1 then we will mention this in the CHANGELOG for said function.
But as it stands, everyone is expected to assume unicode support
everywhere as that's what PHP 6 is all about.
So, it feels right to document unicode compatibility in a few places
like the language reference, features, migration sections, related
extension docs (mbstring/iconv/...)... but not per function. In the
end people will see the light but not be blinded by it ;-) Also it
might be appropriate to document it for each extensions reference.xml
as it will be informative and also help promote this new feature.
Regards,
Philip
On Jul 19, 2006, at 1:03 PM, Gabor Hojtsy wrote:
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.
