Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79152
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender)
References: <C2A085AA-3E3A-405F-954B-4C1F68A46012@ajf.me> <54743ECF.6010301@fischer.name>
Mime-Version: 1.0 (1.0)
In-Reply-To: <54743ECF.6010301@fischer.name>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <B8B6E365-DE64-4DD0-A2EF-9AFBC5DED9FB@ajf.me>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Date: Tue, 25 Nov 2014 10:03:54 +0000
To: Markus Fischer <markus@fischer.name>
Subject: Re: [PHP-DEV] [RFC] Unicode Escape Syntax
From: ajf@ajf.me (Andrea Faulds)


> On 25 Nov 2014, at 08:33, Markus Fischer <markus@fischer.name> wrote:
>=20
>> On 24.11.14 23:09, Andrea Faulds wrote:
>> Good evening,
>>=20
>> Here=E2=80=99s a new RFC: https://wiki.php.net/rfc/unicode_escape
>=20
> I think the choice of \u{xx} is interesting, i.e. using '{' and '}'.
>=20
> Afaik, one of the current best practices is to use json_decode(), like so:=

>=20
> $ cat test.php
> <?php var_dump( json_decode( '"\u00c4"' ) );
>=20
> $ php test.php
> string(2) "=C3=84"

json_decode is an interesting workaround, but JSON suffers from JavaScript, w=
here it got its syntax, having poor Unicode handling. JSON's Unicode escapes=
 only allow BMP characters and, worse, non-BMP characters must be encoded us=
ing surrogate pairs.

--
Andrea Faulds
http://ajf.me/=