On 25/08/16 08:00, Yasuo Ohgaki wrote: > P.S. utf8_decode/encode are "Shouldn't use functions" as they make > code non I18N needlessly. According to the code, original author's > intention was to implement various encoding support. I guess this > wouldn't happen anymore.
Is there any well documented alternative way of achieving the same results as provided by these functions? Much of the time there is on-list debates on how something should be done, but it gets somewhat watered down in a migration guide ... if it makes it there at all. I keep saying it ... just where is the 'best practice' guide to using all the 'new' features of PHP? -- 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
