Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode
| From: | Craig Francis | Date: | Mon, 21 Feb 2022 15:52:57 +0000 |
| Subject: | Re: [RFC] Deprecate and Remove utf8_encode and utf8_decode | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-117102@lists.php.net to get a copy of this message | ||
On Mon, 21 Feb 2022 at 09:09, Rowan Tommins <rowan.collins@gmail.com> wrote:
> 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 "Nguyễn" 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 character
encoding... I assume it's a question of ext/mbstring having all of its
dependencies already present (easier to compile?), vs ext/intl potentially
being more useful (if a little bigger?).
Craig