Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103091
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <41b344e5-51ed-4e81-f6a4-b4f2748fb17e@gmx.de>
References: <41b344e5-51ed-4e81-f6a4-b4f2748fb17e@gmx.de>
Date: Mon, 13 Aug 2018 10:26:29 +0200
Message-ID: <CAF+90c96iDtstS0TyBOJJD_r=KHrtJYnPLqWpQM7-3P0bnKHqg@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a6c37905734cd90f"
Subject: =?UTF-8?B?UmU6IFtQSFAtREVWXSBkZWZhdWx0X2VuY29kaW5nIFJGQyDigJMgYWZ0ZXJtYXRo?=
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000a6c37905734cd90f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sun, Aug 12, 2018 at 7:00 PM, Christoph M. Becker <cmbecker69@gmx.de>
wrote:

> Hi!
>
> Quite a while ago we have accepted the =E2=80=9CUse default_charset As De=
fault
> Character Encoding=E2=80=9D RFC[1], which also contains the clause =E2=80=
=9COld
> iconv.*/mbstring.* php.ini parameters will be removed for master PHP6=E2=
=80=9D
> (obviously that was written before we decided to skip PHP 6, and as such
> would have to be applied to PHP 7).  I'm quite happy, though, that this
> hasn't happened yet, since it seems that the encoding names may be
> different between the extensions.  At least the php.net manual states[2]:
>
> | Some systems (like IBM AIX) use "ISO8859-1" instead of "ISO-8859-1" so
> | this value has to be used in configuration options and function
> | parameters.
>
> It appears to be worthwhile to review the deprecation of the respective
> iconv.* ini options.  Not quite sure about the mbstring.* ini options.
>
> Also, if we stick with the deprecation of the iconv.* ini settings, we
> also should deprecate iconv_set_encoding(), which currently changes the
> deprecated iconv.* ini options, and as such throws a deprecation
> warning.  However, if the ini options would be removed, what should the
> function do?  Nothing?  Change the php.*_encoding settings.  In my
> opinion, both would be rather confusing.  iconv_get_encoding() has a
> similar, albeit minor, issue.
>
> [1] <https://wiki.php.net/rfc/default_encoding>
> [2] <http://php.net/manual/en/iconv.configuration.php>
>

IIRC the new ini settings also don't work with Zend Multibyte yet. That
would need to be fixed before we drop them.

Nikita

--000000000000a6c37905734cd90f--