Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:79621 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32429 invoked from network); 13 Dec 2014 08:57:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Dec 2014 08:57:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=markus@fischer.name; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=markus@fischer.name; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fischer.name from 62.179.121.35 cause and error) X-PHP-List-Original-Sender: markus@fischer.name X-Host-Fingerprint: 62.179.121.35 fep15.mx.upcmail.net Solaris 10 (beta) Received: from [62.179.121.35] ([62.179.121.35:34466] helo=fep15.mx.upcmail.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 38/F0-24726-C8FFB845 for ; Sat, 13 Dec 2014 03:57:49 -0500 Received: from edge02.upcmail.net ([192.168.13.237]) by viefep15-int.chello.at (InterMail vM.8.01.05.13 201-2260-151-135-20130320) with ESMTP id <20141213085744.YOFR8041.viefep15-int.chello.at@edge02.upcmail.net> for ; Sat, 13 Dec 2014 09:57:44 +0100 Received: from mail02.home ([213.47.1.174]) by edge02.upcmail.net with edge id Swxj1p00t3lFLNl01wxjMu; Sat, 13 Dec 2014 09:57:44 +0100 X-SourceIP: 213.47.1.174 Received: from mail02.home ([192.168.1.14] helo=[IPv6:::1]) by mail02.home with esmtp (Exim 4.72) (envelope-from ) id 1XziWE-00074f-SA for internals@lists.php.net; Sat, 13 Dec 2014 09:57:43 +0100 Message-ID: <548BFF86.2040502@fischer.name> Date: Sat, 13 Dec 2014 09:57:42 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam_report: Spam detection software, running on the system "scanner01.home", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On 09.12.14 00:51, Andrea Faulds wrote: > Good evening, > > I’m opening voting on the Unicode Codepoint Escape Syntax RFC. There’s been some discussion in the last two weeks since I introduced the RFC, but there’s nothing left which I feel needs changing. For the character name syntax suggestion (i.e. something like \N{arabic letter alef}), if that’s desired, it could be done later in a different RFC. > > Please read through the RFC and cast your vote if you wish to do so: > > https://wiki.php.net/rfc/unicode_escape > > Voting starts today (2014-12-08) and ends in 10 days’ time (2014-12-18). [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Subject: Re: [PHP-DEV] [VOTE][RFC] Unicode Codepoint Escape Syntax From: markus@fischer.name (Markus Fischer) On 09.12.14 00:51, Andrea Faulds wrote: > Good evening, > > I’m opening voting on the Unicode Codepoint Escape Syntax RFC. There’s been some discussion in the last two weeks since I introduced the RFC, but there’s nothing left which I feel needs changing. For the character name syntax suggestion (i.e. something like \N{arabic letter alef}), if that’s desired, it could be done later in a different RFC. > > Please read through the RFC and cast your vote if you wish to do so: > > https://wiki.php.net/rfc/unicode_escape > > Voting starts today (2014-12-08) and ends in 10 days’ time (2014-12-18). The RFC is really a good writeup, very much appreciated. I've voted no because I'm not entirely convinced the current approach suits PHP long-term. I absolutely appreciate the hard work going into it, no doubt, and I rather have a solution yesterday than tomorrow. But I think a proper Unicode implementation in PHP must not rely on puzzle pieces put together without a clear goal where's we're overall heading. I know that the latter has been tried and failed (multiple times) but that's how I feel about the situation. - Markus