Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:117103
Message-ID: <df1864ca-6504-afad-b6a1-b01c3fa16b73@gmx.de>
Date: Mon, 21 Feb 2022 17:21:42 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Content-Language: de-DE
To: Craig Francis <craig@craigfrancis.co.uk>,
 Rowan Tommins <rowan.collins@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
References: <22242169-a16d-5261-696c-3cf00b00336a@gmail.com>
 <CAFv4g+G2_qmUynYcNNAraXc7UBf1W8viNXda3=WAUwdor+g6PA@mail.gmail.com>
 <93e83a99-8f03-b823-1b4b-a10519d41dd7@gmail.com>
 <CAFv4g+FZQqL_Mbw=obC0AJa6eqZeDaz3+nqtpgZkQOE+ULq_Uw@mail.gmail.com>
 <64095373-f73b-0231-dbd2-3b3271ab0e96@gmail.com>
 <CAFv4g+Heu-Xw_6WhDxVia_WQDuiKWWpf-ccVkmh5HppjCg+P0Q@mail.gmail.com>
In-Reply-To: <CAFv4g+Heu-Xw_6WhDxVia_WQDuiKWWpf-ccVkmh5HppjCg+P0Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Deprecate and Remove utf8_encode and utf8_decode
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 21.02.2022 at 16:52, Craig Francis wrote:

> On Mon, 21 Feb 2022 at 09:09, Rowan Tommins <rowan.collins@gmail.com> wr=
ote:
>
>> Making the extension always available (impossible to compile without it=
)
>> is a potential option, and I think has been suggested before; I'm not
>> sure of the exact pros and cons.
>>
>
> [...]
>
> I would personally encourage everyone to have ext/intl installed and use
>> grapheme_strlen() instead of mb_strlen(), because knowing whether a
>> particular instance of the string "Nguye=CC=82=CC=83n" is written with =
6, 7, or 8
>> code points is not nearly as useful as knowing that it looks like 6
>> "characters" to a user either way.
>
> Good point.
>
> I would like something that can be relied on to convert a strings charac=
ter
> encoding... I assume it's a question of ext/mbstring having all of its
> dependencies already present (easier to compile?), vs ext/intl potential=
ly
> being more useful (if a little bigger?).

We cannot make any extension with external dependencies mandatory.  If
we would require ext/intl, we had to bundle ICU, which is highly
unlikely to happen.  Making ext/mbstring (without ext/mbregex) mandatory
would be an option, but there should be a separate RFC about that.

=2D-
Christoph M. Becker