Re: Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term

Yasuo Ohgaki wrote:

The proper way to handle this is language Unicode support. Having *yet

another* "UTF-8" extension is not a long term solution. Although, it aims to replace existing mbstring, I can agree with your opinion. If PHP is going to support Unicode fully, i.e. have encoding parameter/property, then it would be good solution. Just one quick question, what do you think about encoding parameter/property? Functions like fgetcsv() needs to specify encoding, but it seems many people against it.

The first thing that has to be decided is if the whole core is simply UTF8. To my mind this is the most practical approach, so that fgetcsv() will work only with UTF8. This then moves the problem of coding to where it should be, on the 'connection', so either everything is stored as unicode and transcoded when being saved, or your streaming adds the transcoding. Conversion to lower/upper case would be the same sort of filter on the data stream. -- 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