Re: Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term
| From: | Yasuo Ohgaki | Date: | Wed, 12 Feb 2014 11:18:18 +0000 |
| Subject: | Re: Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72510@lists.php.net to get a copy of this message | ||
Hi Derick,
On Wed, Feb 12, 2014 at 7:17 PM, Derick Rethans <derick@php.net> wrote:
> > All of voters other than me voted no, so far.
> > I would like hear the reason.
>
> 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.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net