Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72510
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.44 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <alpine.DEB.2.10.1402121016191.5374@whisky.home.derickrethans.nl>
References: <CAGa2bXaq+S8hhPW4Mx1KTWjhXk=OL+J5hHWoS-t0Q-5hJOxBow@mail.gmail.com>
 <CAGa2bXYOOXxENG-A+akHf7Q_9Kph+71JPE0JcFXvPKTd0nNFdg@mail.gmail.com> <alpine.DEB.2.10.1402121016191.5374@whisky.home.derickrethans.nl>
Date: Wed, 12 Feb 2014 20:18:18 +0900
Message-ID: <CAGa2bXZDZm1sGds3gv5rG9=XK8U3W7orNV5u3KU9Kb+yixvmLg@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1135e0f432247404f233bd05
Subject: Re: [PHP-DEV] Re: [VOTE] Multbye char handling - Remove vulnerability
 related to multibyte short and long term
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--001a1135e0f432247404f233bd05
Content-Type: text/plain; charset=UTF-8

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

--001a1135e0f432247404f233bd05--