Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122276
MIME-Version: 1.0
References: <CAEPPVa3JWXGLZh9rEE7WGa+nbbfFr-Lv4B7TX4F2TX3OSw6K+Q@mail.gmail.com>
 <CANS-=pcRFH=1y8O6N-R2Ty_Y-xid_i6NM05BPcnKGEdPBhTi_Q@mail.gmail.com> <CANLbj-pYFZj5M+A9=kQW9JobnM7ip0s6FqXA5z5qew6QGRDpfQ@mail.gmail.com>
In-Reply-To: <CANLbj-pYFZj5M+A9=kQW9JobnM7ip0s6FqXA5z5qew6QGRDpfQ@mail.gmail.com>
Date: Fri, 2 Feb 2024 18:27:24 +0900
Message-ID: <CAEPPVa35rq3=UatBKNKNz9aH=FAcc5Fv3yXtUx-b-+uc8W-ppQ@mail.gmail.com>
To: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV][VOTE][RFC] mb_ucfirst and mb_lcfirst functions
From: youkidearitai@gmail.com (youkidearitai)

2024=E5=B9=B42=E6=9C=882=E6=97=A5(=E9=87=91) 18:15 Ayesh Karunaratne <ayesh=
@php.watch>:
>>
>> On Fri, Feb 2, 2024 at 2:00=E2=80=AFAM youkidearitai <youkidearitai@gmai=
l.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 Unicod=
e,
>> it may not behave as expected in some languages. In that case, please de=
al
>> with it in userland.". If my understanding here is wrong, please correct
>> me. ucfirst and lcfirst are to uppercase/lowercase the first character o=
f a
>> word for characters that have an upper/lower case variant. Whether or no=
t 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 m=
e
>> 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 titl=
ecase mappings.
>
> Unicode titlecase mapping is different from uppercase mapping. This PR se=
ems to be using uppercase mapping. This should not matter for a vast majori=
ty of characters, except for ligatures and digraphs.
>
> I'm not at all and expert in these edge cases, but I just wanted to put m=
y two cents forth that I personally think using titlecase mapping on the fi=
rst word would be the more appropriate approach.
>
> Thank you.

Hi, Thank you for reply.

>
> 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 titl=
ecase mappings.
>

Yes, Ayesh is right.
This is a text that is the result of investigating edge cases.

> I'm not at all and expert in these edge cases, but I just wanted to put m=
y two cents forth that I personally think using titlecase mapping on the fi=
rst word would be the more appropriate approach.

I see. I'll change mb_ucfirst using titlecase.
Thank you.

Regards
Yuya

--=20
---------------------------
Yuya Hamada (tekimen)
- https://tekitoh-memdhoi.info
- https://github.com/youkidearitai
-----------------------------