Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36196 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52563 invoked from network); 18 Mar 2008 18:25:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Mar 2008 18:25:13 -0000 Authentication-Results: pb1.pair.com header.from=foolistbar@googlemail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=foolistbar@googlemail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 64.233.182.189 as permitted sender) X-PHP-List-Original-Sender: foolistbar@googlemail.com X-Host-Fingerprint: 64.233.182.189 nf-out-0910.google.com Received: from [64.233.182.189] ([64.233.182.189:19148] helo=nf-out-0910.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 5D/B8-06623-60900E74 for ; Tue, 18 Mar 2008 13:25:11 -0500 Received: by nf-out-0910.google.com with SMTP id e27so19593nfd.13 for ; Tue, 18 Mar 2008 11:25:07 -0700 (PDT) Received: by 10.78.196.10 with SMTP id t10mr2876923huf.30.1205864706300; Tue, 18 Mar 2008 11:25:06 -0700 (PDT) Received: from ?192.168.0.116? ( [86.138.199.53]) by mx.google.com with ESMTPS id e10sm29960337muf.10.2008.03.18.11.25.02 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 18 Mar 2008 11:25:03 -0700 (PDT) Cc: Stephen Bach , internals@lists.php.net Message-ID: <6DC54157-E11D-4F78-AF24-1519E9E05B05@googlemail.com> To: Andrei Zmievski In-Reply-To: <47DFFF31.607@gravitonic.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Tue, 18 Mar 2008 18:25:00 +0000 References: <200803172351.12440.stephen@stephenbach.net> <47DFFF31.607@gravitonic.com> X-Mailer: Apple Mail (2.919.2) Subject: Re: [PHP-DEV] [PATCH] Bug 43477 - Unicode error mode ignored From: foolistbar@googlemail.com (Geoffrey Sneddon) On 18 Mar 2008, at 17:43, Andrei Zmievski wrote: > Why would we not want to stop on illegal sequences? Stuff relies on things _not_ stopping. No web browser stops on an illegal sequence: they all use some replacement character (U+FFFD REPLACEMENT CHARACTER in most). Sure, idealists will say that stopping on errors will get the errors fixed, but that manifestly isn't true. There's a huge amount of ill-formed XML out there. Shipping something that required strings to be valid is just asking to not be used. It breaks too much. We already claim to have error modes that don't stop on error. This is broken. -- Geoffrey Sneddon