<snip>
Also I wonder how a unicode on/off switch will be handled on the documentation side. It would add more permutations in the documentation to have the switch. From my understanding the situation is fairly non trivial already in how to handle all the version dependent differences. Philipp, whats your take on this?
I don't think it matters for documentation because both routes have hurdles and planning requirements. But, it's exciting that we're worrying about this because it's time we educate the world to understand why unicode is useful, and why it's needed today. Andrei asked the documentation team to start the unicode documentation process long ago but given that nobody knows what PHP 6 will be, it makes that tough so we've (for time reasons too) done little. However, each function has a unicode section dedicated to it and general unicode feature sections planned. I don't know if a PHP 6 version of the manual would be a good route to take but it's possible although I prefer shoving information into a users face, both past and present, so said user knows what to look for and worry about in all directions. Each function now has a changelog for that.
In reply to removing the directive, I fear that PHP 6 would be discussed as === PHP 5 + Unicode when this won't be true... yet this idea could persist and cause confusion so let's be sure everyone realizes this from day #.01. It's the main new (and big) feature only, so that's all we can promise. And in this scenario please decide what PHP 7 could be. Would we have 5/7, 7/8, or just 7 with unicode. In other words, coupled PHP versions forever? Or just once. And regardless, we need an effective marketing strategy via PHP.net that does not solely rely on third parties, word of mouth, or PHP's greatness like we've done in the past. This includes the website and documentation, and this includes strong efforts by everyone. Like, explaining ways to be forward compatible. And perhaps PHP 6 will bring with it a new web design, with pictures of little children from all around the world happily holding hands... :-)
So unless something truly innovative seeps up (maybe it has) then stealing ideas from other languages experience and growing pains (like Python and Java) sounds good. If a document existed that compared the situation in many programming languages, the pros and cons, that would be great and might shed light in many of the right places. At least, for me. And/or an update deciphering where we're at after all these lengthy unicode threads. If it's time to go old school with two sides presenting official statements/arguments, then a vote, then so be it. But I don't feel we're quite there yet.
Regards, Philip -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
