Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:71209
Return-Path: <mike.php.net@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 26922 invoked from network); 17 Jan 2014 16:38:04 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 17 Jan 2014 16:38:04 -0000
Authentication-Results: pb1.pair.com smtp.mail=mike.php.net@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=mike.php.net@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender)
X-PHP-List-Original-Sender: mike.php.net@gmail.com
X-Host-Fingerprint: 74.125.83.42 mail-ee0-f42.google.com  
Received: from [74.125.83.42] ([74.125.83.42:50838] helo=mail-ee0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id EC/B1-16023-B6C59D25 for <internals@lists.php.net>; Fri, 17 Jan 2014 11:38:04 -0500
Received: by mail-ee0-f42.google.com with SMTP id e49so2253971eek.1
        for <internals@lists.php.net>; Fri, 17 Jan 2014 08:38:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:subject:from:to:cc:date:in-reply-to:references
         :content-type:mime-version:content-transfer-encoding;
        bh=3W2qCRyPuIJxQ9UtLhIEKl1ObyeH61zZ6QYpDX5/xbc=;
        b=EBidkdOb8u2Lae3+39cfT+2IVYGfX96moC4kMkbiP4B/Gpl+YRz7ovtylnvQjAidJB
         WwN1FZWdcdH4RDN1pCYJQpfaJFs6SayjOWFCtQ9IDNEkr+v4TpXJwNNgZlQhK0gcDOOm
         7MTcimaX9nAV2ZWv/eq+ksSBcCMljbQJOCftBlR49kg2LMDjEW54ph03FHKo4U4VQkeK
         894ZCZY5vKG6otWqYEwXIyw5T3xQDBISVsbPdf4DIqNcIciQ3hodB6xZpDDxhoLwxS0t
         laPB3I/jxx3JdFO0XwY3ardtZyHYmeOhysO5DBoOEKtL5dlh4oeYt51pA2bNVV96Ocrv
         GNEw==
X-Received: by 10.15.51.204 with SMTP id n52mr3706258eew.26.1389976680367;
        Fri, 17 Jan 2014 08:38:00 -0800 (PST)
Received: from [192.168.1.120] (178-18-170-101.customer.bnet.at. [178.18.170.101])
        by mx.google.com with ESMTPSA id j46sm28233542eew.18.2014.01.17.08.37.59
        for <multiple recipients>
        (version=TLSv1 cipher=RC4-SHA bits=128/128);
        Fri, 17 Jan 2014 08:37:59 -0800 (PST)
Message-ID: <1389976678.2057.8.camel@smugmug>
To: Yasuo Ohgaki <yohgaki@ohgaki.net>
Cc: Nikita Popov <nikita.ppv@gmail.com>, "internals@lists.php.net"
	 <internals@lists.php.net>
Date: Fri, 17 Jan 2014 17:37:58 +0100
In-Reply-To: <CAGa2bXb6jLX8HMN-rL7t5j5R_0SaeRkd5r4_MrmQFfsJxxaSxQ@mail.gmail.com>
References: 
	<CAGa2bXauxj6Sca8qYk2cxQ=TeG4bjWgcv-Aqy3cJe35ap72Yfw@mail.gmail.com>
	 <CAF+90c-ZgsCczU71TJap1yeaNhKgQeoUR5oLKwwHHaoOD8z_ig@mail.gmail.com>
	 <CAGa2bXb6jLX8HMN-rL7t5j5R_0SaeRkd5r4_MrmQFfsJxxaSxQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.3 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Multibyte char handling
From: mike.php.net@gmail.com (Mike)

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