>> And, if they don't, unfortunately, it will be one more reason not to >> switch to PHP 6 :) > > I hate to be the one to burst our bubble, but unicode is a killer > feature and PHP 6 will be adopted en masse, so if this isn't changed, it > will simply mean the death of userspace stream wrappers for anything but > custom projects.
You are being optimistic. If PHP6 breaks code, it won't be adopted or adoption will be slow. RFC 2044 was written in October 1996. 10.5 years ago. Unicode v.1.0 standard was written in 1992. People still use other charsets. Outlook Express defaults to ISO-8859-x or CP125x charsets. Mozilla defaults to iso-8859-1. Stock Eudora works only with ISO-8859-1. Lots of sites are written with assumption that client defaults to cp125x or iso-8859-x. IDN is a killer feature and people continue using old ASCII only DNS names. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
