Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121830
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
In-Reply-To: <CAGBsUrd=5WhKERySavP=9yQM-RSkVCwhTJ2oQ4tAQOKTNFoCew@mail.gmail.com>
Date: Tue, 28 Nov 2023 21:09:42 +0100
Cc: Dusk <dusk@woofle.net>,
 Hans Henrik Bergan <divinity76@gmail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <A00495F3-EEB5-4D49-9433-84E94C6920D0@gmail.com>
References: <CAJmy8YFy5RmW1yWuA6akPU31xRz_i1io5uWgt1GWo0n5rzY9EQ@mail.gmail.com>
 <1BA05C1A-AFAE-4E86-BAA2-420B22549519@gmail.com>
 <0D8856BC-DDEE-47F8-8C59-7F4DC7A64237@woofle.net>
 <CAGBsUrd=5WhKERySavP=9yQM-RSkVCwhTJ2oQ4tAQOKTNFoCew@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Subject: Re: [PHP-DEV] Deprecate declare(encoding='...') + zend.multibyte +
 zend.script_encoding + zend.detect_unicode ?
From: claude.pache@gmail.com (Claude Pache)



> Le 28 nov. 2023 =C3=A0 20:56, Kamil Tekiela <tekiela246@gmail.com> a =
=C3=A9crit :
>=20
>> Convert your PHP source files to UTF-8.
>=20
> If the solution is as easy as just converting the encoding of the
> source file, then why did we even need to have this setting at all?
> Why did PHP parser support encodings that demanded the introduction of
> this declare?

It is not necessary as simple: because your code base may contain =
literal strings, and changing the encoding of the source file will =
effectively change the contents of the strings.

=E2=80=94Claude