Re: [Discussion] Should All String Functions Become Multi-Byte Safe?
| From: | Mike Schinkel | Date: | Mon, 12 Aug 2024 16:37:15 +0000 |
| Subject: | Re: [Discussion] Should All String Functions Become Multi-Byte Safe? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-124894@lists.php.net to get a copy of this message | ||
> On Aug 12, 2024, at 5:45 AM, danielhaber@gmail.com wrote:
>
> After reading Rowan's last message, it feels appropriate to link to this:
>
> "The Absolute Minimum Every Software Developer Must Know About Unicode in 2023 (Still No
> Excuses!)"
>
> https://tonsky.me/blog/unicode/ <IܽÂûĪUºÂ7
> {ª https://tonsky.me/blog/unicode/>
Good read! Thank you for mentioning it.
A really standout paragraph from that link is:
"IMO, the whole situation is a shame. Unicode should be
in the stdlib of every language by default. It’s the lingua
franca of the internet! It’s not even new: we’ve been living
with Unicode for 20 years now."
I'll just leave that right here. :-)
-Mike
P.S. Channeling Larry and Derick: https://wiki.php.net/rfc/unicode_text_processing
<https://wiki.php.net/rfc/unicode_text_processing>