Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122275
MIME-Version: 1.0
References: <CAEPPVa3JWXGLZh9rEE7WGa+nbbfFr-Lv4B7TX4F2TX3OSw6K+Q@mail.gmail.com>
 <CANS-=pcRFH=1y8O6N-R2Ty_Y-xid_i6NM05BPcnKGEdPBhTi_Q@mail.gmail.com>
In-Reply-To: <CANS-=pcRFH=1y8O6N-R2Ty_Y-xid_i6NM05BPcnKGEdPBhTi_Q@mail.gmail.com>
Date: Fri, 2 Feb 2024 16:15:16 +0700
Message-ID: <CANLbj-pYFZj5M+A9=kQW9JobnM7ip0s6FqXA5z5qew6QGRDpfQ@mail.gmail.com>
To: Lynn <kjarli@gmail.com>
Cc: youkidearitai <youkidearitai@gmail.com>, php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000009a7de30610628d6e"
Subject: Re: [PHP-DEV][VOTE][RFC] mb_ucfirst and mb_lcfirst functions
From: ayesh@php.watch (Ayesh Karunaratne)

--0000000000009a7de30610628d6e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>
> On Fri, Feb 2, 2024 at 2:00=E2=80=AFAM youkidearitai <youkidearitai@gmail=
.com>
> wrote:
>
> > Hi, Internals
> >
> > I have just opened the voting "Multibyte ucfirst and lcfirst functions"
> > RFC.
> > https://wiki.php.net/rfc/mb_ucfirst
> >
> > Voting will be open until February 26th, 2024 at 01:00 UTC.
> >
> > Cheers
> > Yuya
> >
> > --
> > ---------------------------
> > Yuya Hamada (tekimen)
> > - https://tekitoh-memdhoi.info
> > - https://github.com/youkidearitai
> > -----------------------------
> >
> > --
> > PHP Internals - PHP Runtime Development Mailing List
> > To unsubscribe, visit: https://www.php.net/unsub.php
> >
> >
> In the proposal part is mentioned "From what I've researched with Unicode=
,
> it may not behave as expected in some languages. In that case, please dea=
l
> with it in userland.". If my understanding here is wrong, please correct
> me. ucfirst and lcfirst are to uppercase/lowercase the first character of=
 a
> word for characters that have an upper/lower case variant. Whether or not=
 a
> word _should_ have an uppercase or lower case character is not important
> and currently doesn't behave in such a way for ucfirst and lcfirst. To me
> this isn't unexpected behavior, that's exactly how I would expect it to
> behave.
>

I think the author refers to the potential edge cases in certain Unicode
mappings. There isn't an ucfirst  mapping, but there are uppercase and
titlecase mappings.

Unicode titlecase mapping is different from uppercase mapping. This PR
seems to be using uppercase mapping. This should not matter for a vast
majority of characters, except for ligatures and digraphs.

I'm not at all and expert in these edge cases, but I just wanted to put my
two cents forth that I personally think using titlecase mapping on the
first word would be the more appropriate approach.

Thank you.

>

--0000000000009a7de30610628d6e--