> > The presentation implied that there was vast goals for the project,
> > including a lot of localization features. It seems like some of the
> > smaller features can be worked into a Son-of-Unicode project, and
> > maybe rolled into 5.5?
> 
> it would be a good thing, but nobody stepped up for that, and it
> seems that somehow it isn't really important for the internals.

  This happens in every open source project.  You can't expect a group of open 
source developers to develop what you ask for.  So, it isn't the fault of 
"internals" that no one is stepping up.  Go onto any open source developers 
mailing list, and send a "You guys should do X", and you'll see the exact same 
thing happen.

  On top of that, where is no concept for what Unicode-for-PHP should be.  
There was for the previous (now deemed to have failed) project, including 
UTF16.  But should it be UTF16 or UTF8 or should both be supported?  Unicode 
identifiers...yes or no?  I'm quite interested what everyone's Unicode wishlist 
would look like.


> > But right now, there is this impression of failure, and implication
> > that PHP has no Unicode, because a project to add UTF16 to
> > everything in PHP wasn't completed.
>
> yes there is the impression, Unicode support was the flagship feature
> of the PHP6 release.

  Actually, for me, the deprecated features were far more important than 
Unicode, as I can create Unicode web apps right now.  The PHP Wikipedia page is 
wrong about this too, and states that addslashes() can be used instead of magic 
quotes.  addslashes() should probably be deprecated too (and it isn't Unicode 
aware either, so removing it solves two problems).


> of course we can rationalize the importance of the full unicode
> support, or redefine success, but that won't change the facts that 5
> years of work on I18n was botched with PHP6.

  Five years, without a being able to release even a single minimally 
implemented feature, is definitely a lesson learned.  If you have been coding 
for a year, and there isn't anything that you can release, you need to make 
radical changes to what you've been doing.

> Tyrael

Tom

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to