Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term
| From: | Yasuo Ohgaki | Date: | Wed, 12 Feb 2014 10:06:24 +0000 |
| Subject: | Re: [VOTE] Multbye char handling - Remove vulnerability related to multibyte short and long term | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-72508@lists.php.net to get a copy of this message | ||
Hi all,
On Mon, Feb 10, 2014 at 12:56 PM, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
> Long term: Alternative implementation of mbstring using ICU
> https://wiki.php.net/rfc/altmbstring
> We need multibyte feature as default. However, current mbstring has
> license issues. Resolve license issues by alternative mbstring in the
> future. Introduce mbstring-ng as EXPERIMENTAL module for further
> development, testing, feedback from users.
>
All of voters other than me voted no, so far.
I would like hear the reason.
We can make future PHP handles all encoding. How many of you prefer this
options?
To be honest, I'm +1 for this. However, it seems there are many people
against it.
e.g. Encoding parameter/property seems to have many objections.
Since this is technical discussion, objection without reason is not
constructive.
Thank you for sharing your opinions!
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net