Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79147 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40720 invoked from network); 25 Nov 2014 07:29:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Nov 2014 07:29:06 -0000 Authentication-Results: pb1.pair.com smtp.mail=ivan.enderlin@hoa-project.net; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=ivan.enderlin@hoa-project.net; sender-id=pass Received-SPF: pass (pb1.pair.com: domain hoa-project.net designates 212.85.154.38 as permitted sender) X-PHP-List-Original-Sender: ivan.enderlin@hoa-project.net X-Host-Fingerprint: 212.85.154.38 unknown Received: from [212.85.154.38] ([212.85.154.38:48349] helo=mail.hoa-project.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A0/00-40624-0CF24745 for ; Tue, 25 Nov 2014 02:29:04 -0500 Received: from MacBook-Air-de-Hend.local (206-226.4-85.cust.bluewin.ch [85.4.226.206]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.hoa-project.net (Postfix) with ESMTPSA id 34A8821562 for ; Tue, 25 Nov 2014 08:29:00 +0100 (CET) Message-ID: <54742FBD.802@hoa-project.net> Date: Tue, 25 Nov 2014 08:29:01 +0100 Reply-To: ivan.enderlin@hoa-project.net User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Unicode Escape Syntax From: ivan.enderlin@hoa-project.net ("Ivan Enderlin @ Hoa") Le 24/11/2014 23:09, Andrea Faulds a =C3=A9crit : > Good evening, > > Here=E2=80=99s a new RFC: https://wiki.php.net/rfc/unicode_escape > > It has a rationale section explaining why certain decisions were made, = that I=E2=80=99d recommend you read in full. Excellent RFC, thank you for this proposal. I would suggest this talk=20 https://speakerdeck.com/mathiasbynens/hacking-with-unicode (you might=20 already know) but interesting concepts and limitations of current=20 Unicode implementations are mentioned. The usage of `\u{=E2=80=A6}` fixes most limitations and I could not be mo= re=20 agree with that notation! Cheers. --=20 Ivan Enderlin Developer of Hoa http://hoa-project.net/ PhD. at DISC/Femto-ST (Vesontio) and INRIA (Cassis) http://disc.univ-fcomte.fr/ and http://www.inria.fr/ Member of HTML and WebApps Working Group of W3C http://w3.org/