Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40033 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16677 invoked from network); 21 Aug 2008 01:34:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2008 01:34:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=wrowe@rowe-clan.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=wrowe@rowe-clan.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rowe-clan.net from 64.202.165.38 cause and error) X-PHP-List-Original-Sender: wrowe@rowe-clan.net X-Host-Fingerprint: 64.202.165.38 smtpauth21.prod.mesa1.secureserver.net Received: from [64.202.165.38] ([64.202.165.38:50076] helo=smtpauth21.prod.mesa1.secureserver.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/05-06543-C36CCA84 for ; Wed, 20 Aug 2008 21:34:53 -0400 Received: (qmail 29804 invoked from network); 21 Aug 2008 01:34:49 -0000 Received: from unknown (98.212.183.150) by smtpauth21.prod.mesa1.secureserver.net (64.202.165.38) with ESMTP; 21 Aug 2008 01:34:49 -0000 Message-ID: <48ACC638.1030904@rowe-clan.net> Date: Wed, 20 Aug 2008 20:34:48 -0500 User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Stanislav Malyshev CC: 'PHP Internals' References: <48ACC389.2030801@zend.com> In-Reply-To: <48ACC389.2030801@zend.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] bug #43941 From: wrowe@rowe-clan.net ("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).