Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38575 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24947 invoked from network); 24 Jun 2008 14:21:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Jun 2008 14:21:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:47544] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4E/87-17106-9E201684 for ; Tue, 24 Jun 2008 10:21:31 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 63F6B1EBC014; Tue, 24 Jun 2008 14:23:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XjLgOG89QiCu; Tue, 24 Jun 2008 16:23:53 +0200 (CEST) Received: from [192.168.80.139] (unknown [195.226.16.50]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id 77FC71EBC012; Tue, 24 Jun 2008 16:23:52 +0200 (CEST) Cc: Andi Gutmans , Stas Malyshev , Steph Fox , internals Message-ID: <1E9C3FFB-159E-47CC-8BE9-54180AA3356A@pooteeweet.org> To: Derick Rethans In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Tue, 24 Jun 2008 16:20:24 +0200 References: <00cf01c8c242$f1a6ce10$4401a8c0@foxbox> <10845a340805300354y35e28f30r30eb6e8edebf0ef1@mail.gmail.com> <48422F7C.1030002@zend.com> <698DE66518E7CA45812BD18E807866CE01B113E1@us-ex1.zend.net> X-Mailer: Apple Mail (2.924) Subject: Re: [PHP-DEV] New flame From: mls@pooteeweet.org (Lukas Kahwe Smith) On 24.06.2008, at 16:10, Derick Rethans wrote: > On Mon, 16 Jun 2008, Andi Gutmans wrote: > >>> From: Lukas Kahwe Smith [mailto:mls@pooteeweet.org] >>> >>>> I was under impression parser multibyte support wasn't yet fixed. >>>> Was it? >>> >>> Maybe we should decide if this a show stopper or not. From my >>> understanding we still do not have any example of this being used in >>> the wild .. >> >> This is used when reading scripts that are in encodings like Shift- >> JIS >> which is very common in Japan. In any case, I have tried to get >> involvement from some people I know over there without much success. > > I've asked around a bit as well with our customers/partners, and all > they seem to answer is "we simply use UTF-8". At this point there is no 1st hand user known. There is no example code. At the same time a lot of core developers question if the code is even able to work in any reliable and secure way. Finally the feature is not even documented. As such the conclusion can only be that investing any time in readding this "feature" would be a bad idea. If anyone actually uses this feature they will have to come out of the woodwork now or when 5.3 is out. At this point we might have enough information to actually understand how that feature is used and how we can add it to 5.3. regards, Lukas Kahwe Smith mls@pooteeweet.org