Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113653
MIME-Version: 1.0
References: <f313c9c4-f8a2-0b39-7499-30620d80cecd@gmail.com>
 <3a4d89fc-c5f8-4720-b2e0-f6f3c28684f9@www.fastmail.com> <5f5fd136-e181-d5d3-fe40-1a4cc5c668f2@gmail.com>
 <CAGBsUrcsms0TfnwnrjyaugmDd549gHbTTDj+VoR1sPzm9-8TGw@mail.gmail.com>
In-Reply-To: <CAGBsUrcsms0TfnwnrjyaugmDd549gHbTTDj+VoR1sPzm9-8TGw@mail.gmail.com>
Date: Mon, 22 Mar 2021 00:00:37 +0300
Message-ID: <CAGgaK7LDeX0nGggpQbNROD91Mgg=g0RJTvpP5d47yEYzjOR1hA@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: Rowan Tommins <rowan.collins@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000005d79e205be123ec3"
Subject: Re: [PHP-DEV] What should we do with utf8_encode and utf8_decode?
From: maxsem.wiki@gmail.com (Max Semenik)

--0000000000005d79e205be123ec3
Content-Type: text/plain; charset="UTF-8"

On Sun, Mar 21, 2021 at 10:08 PM Kamil Tekiela <tekiela246@gmail.com> wrote:

> I think we really do not need to keep these functions. As for the
> alternative that we can offer, iconv seems to be doing exactly the same
> thing and even better. mb_convert_encoding does the same but also silently
> ignores invalid characters. So we already offer plenty of alternatives. We
> don't need to add anything new.
>

Just a quick reminder that it's possible to compile PHP without mbstring
and intl, which means that some hosts will provide PHP without these
extensions, and some packagers make them available as separate packages
that users can't or don't know how to install. Maybe we've got an
opportunity to think about making these extensions mandatory?

-- 
Best regards,
Max Semenik

--0000000000005d79e205be123ec3--