Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122799
Feedback-ID: id4f946ef:Fastmail
User-Agent: Cyrus-JMAP/3.11.0-alpha0-333-gbfea15422e-fm-20240327.001-gbfea1542
Precedence: bulk
MIME-Version: 1.0
Message-ID: <1dfd354a-898c-4721-818c-0284191354a5@app.fastmail.com>
In-Reply-To: <4952eb36-1c45-4b6f-ae62-fa641e391246@rwec.co.uk>
References: 
 <CAEPPVa0RKdhCcogf+z77rgLK5xw55R-1VBo-z8pFPKNBH3u34A@mail.gmail.com>
 <CAEPPVa2SW5uDZCS_oESk1k-RMyjuYNmLa+=xFYHb4QXhOQGc=A@mail.gmail.com>
 <CANLbj-q10+Fiz7zvnHpUgL49KNA7DCYxq21vK3gPbSpDq-BHag@mail.gmail.com>
 <CA+XhMqzgd0vyC_qB0-4an4kTNuH9ayFqshs6PdQMweyOxBw1Fg@mail.gmail.com>
 <CAEPPVa0O9qZY88wry7Ox_hRq44L6xnMboTGvPCv_GC2ZfHu5EA@mail.gmail.com>
 <141e31f3-b7cf-4bd1-9bac-c9ec078767ed@app.fastmail.com>
 <E82F0279-47D8-4BC1-9281-45799B7C018C@php.net>
 <216d4a09-7921-48f6-b892-8d9605d367ab@app.fastmail.com>
 <4952eb36-1c45-4b6f-ae62-fa641e391246@rwec.co.uk>
Date: Thu, 28 Mar 2024 22:25:11 +0100
To: "Levi Morrison" <internals@lists.php.net>
Subject: Re: [PHP-DEV][RFC] grapheme cluster for str_split, grapheme_str_split function
Content-Type: multipart/alternative;
 boundary=5ba9b3f1d27d4b798c20d37e91168ef1
From: langemeijer@php.net ("Casper Langemeijer")

--5ba9b3f1d27d4b798c20d37e91168ef1
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable



> So... if you want to help make people more aware of the grapheme_*=20
> functions, one place to start would be editing the documentation for t=
he=20
> various string, mbstring, and grapheme functions to use consistent=20
> terminology, and sign-post each other more clearly.=20
> http://doc.php.net/tutorial/

Yes I agree, Also I've edited documentation before in the svn days. I al=
ready planned to read up on how this is working nowadays.

Also I'm planning an outline for a conference talk on the subject. I've =
educated people on unicode related subjects before, and think I have a f=
ew very good stories that can give insight into this for unsuspecting de=
velopers.

I love the analogy that most Europeans understand. For the city of Colog=
ne, there are two equally valid ways to write it's German name. K=C3=B6l=
n and Koeln. (Used when hindered by technical limitations, or maybe in i=
nformal conversation) Every German can extra_e_decode() and extra_e_enco=
de(). Same for Stra=C3=9Fe and Strasse.

Ligatures in fonts make it harder though, sometimes they intentionally o=
bfuscate what's happening in the unicode layer. You might know this from=
 special programming fonts with glyphs for =3D=3D=3D, <> and such.

Some Dutch fonts do a special ligature that combines ij, which was in th=
e Dutch alphabet when I was a kid, 'y' was not. Unicode U+0132 and U+013=
3 describe this symbol, but I've never seen them used. Fonts combining i=
j to one visual entity is more common.

I imagine most languages and cultures have these kind of edge-cases.


--5ba9b3f1d27d4b798c20d37e91168ef1
Content-Type: text/html;charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso=
Normal,p.MsoNoSpacing{margin:0}</style></head><body><div><br></div><div>=
<br></div><blockquote type=3D"cite" id=3D"qt" style=3D""><div>So... if y=
ou want to help make people more aware of the grapheme_*&nbsp;<br></div>=
<div>functions, one place to start would be editing the documentation fo=
r the&nbsp;<br></div><div>various string, mbstring, and grapheme functio=
ns to use consistent&nbsp;<br></div><div>terminology, and sign-post each=
 other more clearly.&nbsp;<br></div><div><a href=3D"http://doc.php.net/t=
utorial/">http://doc.php.net/tutorial/</a><br></div></blockquote><div><b=
r></div><div>Yes I agree, Also I've edited documentation before in the s=
vn days. I already planned to read up on how this is working nowadays.<b=
r></div><div><br></div><div>Also I'm planning an outline for a conferenc=
e talk on the subject. I've educated people on unicode related subjects =
before, and think I have a few very good stories that can give insight i=
nto this for unsuspecting developers.<br></div><div><br></div><div>I lov=
e the analogy that most Europeans understand. For the city of Cologne, t=
here are two equally valid ways to write it's German name. K=C3=B6ln and=
 Koeln. (Used when hindered by technical limitations, or maybe in inform=
al conversation) Every German can extra_e_decode() and extra_e_encode().=
 Same for Stra=C3=9Fe and Strasse.<br></div><div><br></div><div>Ligature=
s in fonts make it harder though, sometimes they intentionally obfuscate=
 what's happening in the unicode layer. You might know this from special=
 programming fonts with glyphs for =3D=3D=3D, &lt;&gt; and such.<br></di=
v><div><br></div><div>Some Dutch fonts do a special ligature that combin=
es ij, which was in the Dutch alphabet when I was a kid, 'y' was not. Un=
icode U+0132 and U+0133 describe this symbol, but I've never seen them u=
sed. Fonts combining ij to one visual entity is more common.<br></div><d=
iv><br></div><div>I imagine most languages and cultures have these kind =
of edge-cases.</div><div><br></div><div><br></div></body></html>
--5ba9b3f1d27d4b798c20d37e91168ef1--