Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:130386
Precedence: list
MIME-Version: 1.0
References: <CAEPPVa3S+CeCzK+EY7CY6B=C5Mt0ePKq7E-HQwSR=fQ0zap1Bg@mail.gmail.com>
 <CAEPPVa3Y41+_6TD6Ae8Sph10USuTC0w-tqB3N+kc1wh=nmF5CA@mail.gmail.com>
 <8d1d90e2-b2db-421a-babe-f915dc06b76d@gmx.de> <d7e178e0-6040-e7aa-0ef2-ff011815ff44@php.net>
 <CAEPPVa1NnuLruP5KW5HvoQU+1gAiVw_1ekE2xLGS1jX6njL1RQ@mail.gmail.com>
 <CAJmy8YGsuh0owDGSrb1gnsRwK53bN4UaX1p_B+CSqfiDQqRG5w@mail.gmail.com> <CAGBsUrcURj8hxFpgoR2TguR8_ykW72gfp4qjv3E418bquR82VA@mail.gmail.com>
In-Reply-To: <CAGBsUrcURj8hxFpgoR2TguR8_ykW72gfp4qjv3E418bquR82VA@mail.gmail.com>
Date: Wed, 18 Mar 2026 04:52:42 +0900
Message-ID: <CAEPPVa1uTiz_uYuwisu77omEpaee5BCW=MuymTXpLbQP=9CQQA@mail.gmail.com>
Subject: Re: [PHP-DEV][DISCUSSION] Deprecate mbregex in PHP 8.6 and
 maintenance version
To: php internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
From: youkidearitai@gmail.com (youkidearitai)

2026=E5=B9=B43=E6=9C=8818=E6=97=A5(=E6=B0=B4) 2:31 Kamil Tekiela <tekiela24=
6@gmail.com>:
>
> On Tue, 17 Mar 2026 at 17:07, Hans Henrik Bergan <divinity76@gmail.com> w=
rote:
> >
> >
> >
> > On Tue, 17 Mar 2026 at 09:43, youkidearitai <youkidearitai@gmail.com> w=
rote:
> >>
> >> 2025=E5=B9=B48=E6=9C=8826=E6=97=A5(=E7=81=AB) 19:15 Derick Rethans <de=
rick@php.net>:
> >> >
> >> > On Mon, 25 Aug 2025, Christoph M. Becker wrote:
> >> >
> >> > > On 25.08.2025 at 09:26, youkidearitai wrote:
> >> > >
> >> > > > I improvement this RFC. https://wiki.php.net/rfc/eol-oniguruma
> >> > > >
> >> > > > Added more information about maintenance versions. What do you t=
hink
> >> > > > about Oniguruma maintenance ended. Please watch and feel free to
> >> > > > comment.
> >> > >
> >> > > First, thank you for caring about this!  I agree that we need a lo=
ng
> >> > > term solution for this issue.  As I understand it, Oniguruma's
> >> > > greatest advantage over PCRE2 is that it supports other character
> >> > > encodings than Unicode and ANSI, so deprecating mbregex might be a
> >> > > problem for some users.
> >
> >
> > Which users, exactly?
> >
> > Where in the wild are people using something other than ANSI, Unicode, =
and UTF-8?
> >
> > Been 10 year since I was involved with a system reliant on Windows-1252=
, and the first thing I did after getting hired was to convert it to UTF-8
> > (Norway, a system written in PHP requiring =C3=A6=C3=B8=C3=A5=C3=86=C3=
=98=C3=85 support running on Windows-1252~)
>
> I found this example on Wikipedia view-source:https://kakaku.com/
> https://kakaku.com/

Hi
I explain why create mb_onig package.

First, many users reported depends on Oniguruma and mbregex.
For example, Phiki https://github.com/phikiphp/phiki users reported.
https://github.com/php/php-src/pull/19258#issuecomment-3249570139
In Wikipedia, we can see many depends on Oniguruma.
https://en.wikipedia.org/wiki/Oniguruma

Second, FreeBSD supports end Oniguruma in Dec 2026(this year).
https://github.com/php/php-src/pull/19258#issuecomment-3506659061

Therefore, FreeBSD can't compile mbregex after Dec 2026.
I want to avoid it.

> > Been 10 year since I was involved with a system reliant on Windows-1252=
, and the first thing I did after getting hired was to convert it to UTF-8
This point is good perspective, Not opensource products maybe depends
mbregex in old codes.
It is maintenance very long time.(My company products depends mbregex)

So I want to maintenance Oniguruma and mbregex other way.
My solution(mb_onig) is one way.

Regards
Yuya

--=20
---------------------------
Yuya Hamada (tekimen)
- https://tekitoh-memdhoi.info
- https://github.com/youkidearitai
-----------------------------