Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31269
Return-Path: <philip@roshambo.org>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 56352 invoked by uid 1010); 25 Jul 2007 17:15:51 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 56336 invoked from network); 25 Jul 2007 17:15:50 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 25 Jul 2007 17:15:50 -0000
Authentication-Results: pb1.pair.com smtp.mail=philip@roshambo.org; spf=permerror; sender-id=unknown
Authentication-Results: pb1.pair.com header.from=philip@roshambo.org; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain roshambo.org from 207.210.105.50 cause and error)
X-PHP-List-Original-Sender: philip@roshambo.org
X-Host-Fingerprint: 207.210.105.50 analucia.asmallorange.com  
Received: from [207.210.105.50] ([207.210.105.50:55305] helo=analucia.asmallorange.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id C7/67-02163-44587A64 for <internals@lists.php.net>; Wed, 25 Jul 2007 13:15:50 -0400
Received: from c-24-20-30-252.hsd1.mn.comcast.net ([24.20.30.252]:8535 helo=[192.168.3.104])
	by analucia.asmallorange.com with esmtpa (Exim 4.66)
	(envelope-from <philip@roshambo.org>)
	id 1IDkSh-0003At-El; Wed, 25 Jul 2007 13:15:47 -0400
In-Reply-To: <469DE3A0.1060902@pooteeweet.org>
References: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net> <54C4340A-D9EA-4B5A-B39C-B55B29B1B3BC@prohost.org> <698DE66518E7CA45812BD18E807866CE648193@us-ex1.zend.net> <469B7FB1.1070507@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE648290@us-ex1.zend.net> <fe05d1540707170021y423f7d81kd1ab28a5719630fb@mail.gmail.com> <7.0.1.0.2.20070718023255.0dc0eed0@zend.com> <alpine.DEB.0.98.0707181014230.10300@kossu.ez.no> <469DE09F.9080509@lerdorf.com> <469DE3A0.1060902@pooteeweet.org>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-ID: <9DA2114F-30EB-4FEF-A487-EDBF0D3D6B37@roshambo.org>
Cc: Rasmus Lerdorf <rasmus@lerdorf.com>,
 Derick Rethans <derick@php.net>,
 PHP Developers Mailing List <internals@lists.php.net>
Content-Transfer-Encoding: 7bit
Date: Wed, 25 Jul 2007 10:15:32 -0700
To: Lukas Kahwe Smith <mls@pooteeweet.org>
X-Mailer: Apple Mail (2.752.3)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - analucia.asmallorange.com
X-AntiAbuse: Original Domain - lists.php.net
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - roshambo.org
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [PHP-DEV] POSIX regex
From: philip@roshambo.org (Philip Olson)

<snip>
> Also I wonder how a unicode on/off switch will be handled on the  
> documentation side. It would add more permutations in the  
> documentation to have the switch. From my understanding the  
> situation is fairly non trivial already in how to handle all the  
> version dependent differences. Philipp, whats your take on this?

I don't think it matters for documentation because both routes have  
hurdles and planning requirements. But, it's exciting that we're  
worrying about this because it's time we educate the world to  
understand why unicode is useful, and why it's needed today. Andrei  
asked the documentation team to start the unicode documentation  
process long ago but given that nobody knows what PHP 6 will be, it  
makes that tough so we've (for time reasons too) done little.  
However, each function has a unicode section dedicated to it and  
general unicode feature sections planned. I don't know if a PHP 6  
version of the manual would be a good route to take but it's possible  
although I prefer shoving information into a users face, both past  
and present, so said user knows what to look for and worry about in  
all directions. Each function now has a changelog for that.

In reply to removing the directive, I fear that PHP 6 would be  
discussed as === PHP 5 + Unicode when this won't be true... yet this  
idea could persist and cause confusion so let's be sure everyone  
realizes this from day #.01. It's the main new (and big) feature  
only, so that's all we can promise. And in this scenario please  
decide what PHP 7 could be. Would we have 5/7, 7/8, or just 7 with  
unicode. In other words, coupled PHP versions forever? Or just once.  
And regardless, we need an effective marketing strategy via PHP.net  
that does not solely rely on third parties, word of mouth, or PHP's  
greatness like we've done in the past. This includes the website and  
documentation, and this includes strong efforts by everyone. Like,  
explaining ways to be forward compatible. And perhaps PHP 6 will  
bring with it a new web design, with pictures of little children from  
all around the world happily holding hands... :-)

So unless something truly innovative seeps up (maybe it has) then  
stealing ideas from other languages experience and growing pains  
(like Python and Java) sounds good. If a document existed that  
compared the situation in many programming languages, the pros and  
cons, that would be great and might shed light in many of the right  
places. At least, for me. And/or an update deciphering where we're at  
after all these lengthy unicode threads. If it's time to go old  
school with two sides presenting official statements/arguments, then  
a vote, then so be it. But I don't feel we're quite there yet.

Regards,
Philip