Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79155
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.220.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <24EE758F-BF8F-4AE9-B793-20739CD9875D@ajf.me>
References: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me>
	<CA+9eiLsNHZMTgV0EZFXxYmAx+sE-qbgPrTYE0rH=bFLpSq2rdg@mail.gmail.com>
	<24EE758F-BF8F-4AE9-B793-20739CD9875D@ajf.me>
Date: Tue, 25 Nov 2014 14:41:48 +0400
Message-ID: <CA+9eiLvxt=H8w_VTgL-0sTS19DJzdouX4peBzQXFuWmNefwH+w@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1135fa5aef38250508ac8e41
Subject: Re: [PHP-DEV] [RFC] Unicode Escape Syntax
From: dmitry@zend.com (Dmitry Stogov)

--001a1135fa5aef38250508ac8e41
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 25, 2014 at 1:00 PM, Andrea Faulds <ajf@ajf.me> wrote:

>
> > On 25 Nov 2014, at 08:33, Dmitry Stogov <dmitry@zend.com> wrote:
> >
> > May be I misunderstood something, but why to introduce unicode escapes
> if PHP engine doesn't support Unicode.
>
> We don't have Unicode strings which are made of codepoints rather than
> bytes, sure. But we do usually treat these strings as UTF-8. The idea of
> doing this in a language without Unicode strings isn't new, C/C++ have th=
e
> u8"" syntax for making UTF-8 strings.
>

u8"string" tells that the whole string is UTF-8 encoded.
Your escape Unicode proposal  assumes just UTF-8 codepoint, but the whole
string encoding is still undefined.


>
> > Always converting such escapes into UTF-8 encoding, doesn't make any
> sense for people who use other encodings for output, databases, etc.
>
> If you're using other encodings, why do you want to use a Unicode
> codepoints? Most Unicode codepoints will not supported by another charact=
er
> set.
>

Agree, this Unicode escapes are not going to be used for anything except
UTF-8 encoded strings.
I'm not completely against it. It's just an incomplete solution.

echo "\u{1F602}"; // won't output =F0=9F=98=82 if the output encoding is no=
t UTF-8

echo "=D0=9F=D1=80=D0=B8=D0=B2=D0=B5=D1=82 \u{1F602}"; // won't output anyt=
hing useful if script
encoding is not UTF-8

The second problem present even for European counties that use Windows-1250
codepage.

echo "ma=C3=B1ana \u{1F602}"; // won't output anything useful if script
encoding is not UTF-8

Thanks. Dmitry.


>
> --
> Andrea Faulds
> http://ajf.me/
>

--001a1135fa5aef38250508ac8e41--