On Fri, 2014-01-17 at 07:34 +0900, Yasuo Ohgaki wrote:
> This discussion circulate discussion.
I'm also in favor of putting those things in ext/mbstring.
>
> At first, I proposed locale based solution using php_mblen().
> This approach does not require additional encoding parameter
> since encoding is specified by locale.
Meh, but would be okay for me.
>
> However, some people don't like the solution (in security ML)
> because it is locale based solution. It may have unwanted side
> effects. Locale is unreliable and most user just don't care about it.
>
> Therefore, I proposed this approach that introduce encoding
> parameter just like htmlspecialchars()/htmlentities().
>
> Encoding parameter (or some way to specify encoding) for security
> related string function is mandatory. We should provide some way
> to specify encoding.
>
Many of us do not have access to that mailing list, so yould you shed
some light on the acutal issue?
--
Regards,
Mike