On 08/03/15 10:03, Grégory Planchat wrote: > Then using multiple encodings in a same script or using a same script > for multiple encodings becomes straightforward and standard. Most PHP > developers doesn't even know what is Unicode or a character encoding, > they just see "odd characters that are removed with a header() call or > utf8_decode()", no teasing intended, they just don't want to have to > handle this. PHP should not let this sort of consideration to the sole > awareness of user-space developers.
Not part of THIS discussion exactly, but I have to take that in isolation. 'Most PHP developers' need to be very aware of Unicode these days. Simply pretending it does not exist is a deangerous exercise and my own code base has been UTF8 for several years now. Even though I don't speak anything but English, a large section of the material one has to handle has characters which get lost if one does not maintain UTF8 through out the process. People are going on about 'data loss' when converting, and that applies equally to strings as numbers. The default encoding these days is UTF8 ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
