Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47698 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87551 invoked from network); 31 Mar 2010 23:13:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Mar 2010 23:13:17 -0000 Authentication-Results: pb1.pair.com header.from=jacob@oettinger.dk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=jacob@oettinger.dk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain oettinger.dk from 74.125.78.24 cause and error) X-PHP-List-Original-Sender: jacob@oettinger.dk X-Host-Fingerprint: 74.125.78.24 ey-out-2122.google.com Received: from [74.125.78.24] ([74.125.78.24:13928] helo=ey-out-2122.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/82-04237-B07D3BB4 for ; Wed, 31 Mar 2010 18:13:16 -0500 Received: by ey-out-2122.google.com with SMTP id d26so51275eyd.39 for ; Wed, 31 Mar 2010 16:13:13 -0700 (PDT) Received: by 10.213.65.204 with SMTP id k12mr2703323ebi.15.1270077192132; Wed, 31 Mar 2010 16:13:12 -0700 (PDT) Received: from [192.168.1.3] ([80.197.103.249]) by mx.google.com with ESMTPS id 14sm4066410ewy.6.2010.03.31.16.13.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Mar 2010 16:13:11 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 1 Apr 2010 01:13:09 +0200 Message-ID: To: internals@lists.php.net Mime-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) Subject: Wiki-page for unicode status and ideas From: jacob@oettinger.dk (Jacob Oettinger) Hi David Z=FClke kindly let me know that I mis-posted the message below by = posting it as a reply with a different subject. So here it is again, now = in its own thread. (sorry about the double post) Hi all, I have been following the internals list since I heard that the unicode = effort had grinded to a halt (so I am quite the noob into the php = internals world). I have some ideas for possible ways to implement unicode handling. My = guess is that most of these have been discussed earlier but I do not = seem to be able to find any good way of reading up on the choices that = led to the php 6 unicode implementation (please direct me in the right = direction if such a source is available). It would also be great if = there was a source of information that listed some of the caveats of the = project that I am guessing is what is making it hard to implement. I proppose that we make a wiki page that attempts to summarize = information about unicode support in php. Some of the headlines on the = page could be: * Desired features * Cavets * The "php 6 way" * Possible alternative "ways" I think this would give a good overview that would make it easier to = make the right decision on how to move forward. I would like to organize/collect/manage the information, but I need help = in finding the needed information. Is this a good idea? Is it silly to have someone, that has not been involved in the earlier = unicode discussions, trying to summarize on them? Regards, Jacob Oettinger=