Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:70926
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH8MpnnF+O32tC2ybXfRc3=yVez5ra-EQsA-fTsmLsf_5Kyj0Q@mail.gmail.com>
References: <CAH8MpnnF+O32tC2ybXfRc3=yVez5ra-EQsA-fTsmLsf_5Kyj0Q@mail.gmail.com>
Date: Mon, 30 Dec 2013 21:38:46 +0100
Message-ID: <CAF+90c_TPYOhM_Xs2cMPB_gPE7Lv=mZhq7r3K5cc20neE99SYQ@mail.gmail.com>
To: Daniel Lowrey <rdlowrey@php.net>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e01182c7e38c9f204eec66e73
Subject: Re: [PHP-DEV] Re: Default character encoding
From: nikita.ppv@gmail.com (Nikita Popov)

--089e01182c7e38c9f204eec66e73
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Dec 30, 2013 at 8:38 PM, Daniel Lowrey <rdlowrey@php.net> wrote:

> > PHP 5.6 and master, introduce new php.ini settting. Old
> > iconv.*/mbstring.* php.ini parameters will be removed for master.
>
> If I understand the RFC correctly shouldn't the use of the old/existing
> functions trigger an E_DEPRECATED error as of 5.6 to funnel users into the
> new settings? I don't see this anywhere in the associated patch. Shouldn't
> this be included or have I misunderstood?
>

Context: https://wiki.php.net/rfc/default_encoding

I'm also a bit concerned about this RFC in general. I think the idea behind
it make sense (consolidate encoding settings), but right now it feels a lot
like http://xkcd.com/927/ (turning 6 ini options into 9). Especially given
the issue with the different charset names between mbstring and iconv, I'm
not convinced that this will be more help than harm.

Also, the most important part of the RFC (htmlspecialchars) doesn't seem
reflected in the patch. Is that not yet implemented or did I misunderstand
something?

Nikita

--089e01182c7e38c9f204eec66e73--