Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40043 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19950 invoked from network); 21 Aug 2008 10:50:08 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2008 10:50:08 -0000 Authentication-Results: pb1.pair.com header.from=david.zuelke@bitextender.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=david.zuelke@bitextender.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain bitextender.com from 80.237.132.12 cause and error) X-PHP-List-Original-Sender: david.zuelke@bitextender.com X-Host-Fingerprint: 80.237.132.12 wp005.webpack.hosteurope.de Received: from [80.237.132.12] ([80.237.132.12:44602] helo=wp005.webpack.hosteurope.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/07-06543-E584DA84 for ; Thu, 21 Aug 2008 06:50:07 -0400 Received: from munich.bitxtender.net ([85.183.90.3] helo=[10.224.254.2]); authenticated by wp005.webpack.hosteurope.de running ExIM using esmtpsa (TLSv1:RC4-SHA:128) id 1KW7jv-0000XN-8x; Thu, 21 Aug 2008 12:50:03 +0200 Cc: Stanislav Malyshev , 'PHP Internals' Message-ID: <7C51580F-C656-47D9-9269-CA140AA9EBC2@bitextender.com> To: "William A. Rowe, Jr." In-Reply-To: <48ACC638.1030904@rowe-clan.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v926) Date: Thu, 21 Aug 2008 12:50:02 +0200 References: <48ACC389.2030801@zend.com> <48ACC638.1030904@rowe-clan.net> X-Mailer: Apple Mail (2.926) X-bounce-key: webpack.hosteurope.de;david.zuelke@bitextender.com;1219315807;2e79164a; Subject: Re: [PHP-DEV] bug #43941 From: david.zuelke@bitextender.com (=?ISO-8859-1?Q?David_Z=FClke?=) Am 21.08.2008 um 03:34 schrieb William A. Rowe, Jr.: > Stanislav Malyshev wrote: >> Hi! >> Are there any objections to incorporating bugfix for #43941 (fix >> for how json handles invalid UTF-8 sequences) into 5.2? I had some >> requests about it, right now it's only in 5.3+. > > Is there the alternative of substituting an unmappable character > FFFD in > place of the invalid sequence? This a a reasonable alternative > behavior > for some less stringent cases. > > (Yes, the fix is better than the status quo, but just taking this a > step > further). I agree, that would be quite reasonable and also more consistent with how UTF-8 works in other apps (browsers etc). David