Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:124863
Precedence: bulk
MIME-Version: 1.0
References: <8a60a5d76bf3bbdda821160c6141b45914a33b98.camel@ageofdream.com> <fe3aaa5d-109e-46be-afd4-93b10e66f8f1@sandfox.me>
In-Reply-To: <fe3aaa5d-109e-46be-afd4-93b10e66f8f1@sandfox.me>
Date: Mon, 12 Aug 2024 02:03:08 +0900
Message-ID: <CAEPPVa1wHe=5AzAya=VyCwB+6d-ehJUNySFh7BU2269U+jPHsQ@mail.gmail.com>
Subject: Re: [PHP-DEV][Discussion] Should All String Functions Become
 Multi-Byte Safe?
To: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: youkidearitai@gmail.com (youkidearitai)

2024=E5=B9=B48=E6=9C=8812=E6=97=A5(=E6=9C=88) 1:42 Anton Smirnov <sandfox@s=
andfox.me>:
>
> Hi Nick,
>
> As a developer who often deals with binary data (like bencode, ipv6
> addresses and my own hacks for multibyte arithmetic) I would prefer that
> functions and syntaxes that allow me to work with bytes keep working
> with bytes, not characters or code points. So the closest solution would
> be separate binary/text strings, but then we have PHP6 all over again.
> Maybe this time it might work in some form, who knows.
>
> On 8/11/24 18:50, Nick Lockheart wrote:
> >
> > HTML 5 was adopted in 2014, over ten years ago. HTML 5 only supports
> > the UTF-8 multi-byte character encoding.
> >
> > It seems like there's still a lot of string functions that assume that
> > a character is a single byte, and these may actually work as expected
> > when dealing with Latin characters, but may fail unexpectedly if a
> > sequence is more than one byte.
> >
> > Are there any use cases for PHP where **single-byte** characters are
> > the norm?
> >
> > It seems that if everything on the Internet is multi-byte encoded now,
> > then all of the PHP string functions should be multi-byte safe.
> >
> >
> > The WHATWG Encoding Standard:
> >
> > https://encoding.spec.whatwg.org/
> >
> > Also, according to Mozilla, "[The meta charset] attribute declares the
> > document's character encoding. If the attribute is present, its value
> > must be an ASCII case-insensitive match for the string "utf-8", because
> > UTF-8 is the only valid encoding for HTML5 documents."
> >
> > https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#charset

Hi Nick

I'm confused what is "multibyte safe".

Usually, PHP's string type is binary.
https://www.php.net/manual/en/language.types.string.php

If you want to use multibyte character, you can use mbstring functions.
(Is "multibyte safe" says about mbstring functions?)
https://www.php.net/manual/en/book.mbstring.php

There is no consistent solution I think, because you have to think a
lot about multibyte characters.

Regards
Yuya

--=20
---------------------------
Yuya Hamada (tekimen)
- https://tekitoh-memdhoi.info
- https://github.com/youkidearitai
-----------------------------