Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73764 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 60141 invoked from network); 22 Apr 2014 09:45:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Apr 2014 09:45:10 -0000 Authentication-Results: pb1.pair.com header.from=lester@lsces.co.uk; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lester@lsces.co.uk; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.204 cause and error) X-PHP-List-Original-Sender: lester@lsces.co.uk X-Host-Fingerprint: 217.147.176.204 mail4.serversure.net Linux 2.6 Received: from [217.147.176.204] ([217.147.176.204:45306] helo=mail4.serversure.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/91-45364-32A36535 for ; Tue, 22 Apr 2014 05:45:09 -0400 Received: (qmail 8250 invoked by uid 89); 22 Apr 2014 09:45:04 -0000 Received: by simscan 1.3.1 ppid: 8243, pid: 8247, t: 0.0707s scanners: attach: 1.3.1 clamav: 0.96/m:52 Received: from unknown (HELO linux-dev4.lsces.org.uk) (lester@rainbowdigitalmedia.org.uk@81.138.11.136) by mail4.serversure.net with ESMTPA; 22 Apr 2014 09:45:04 -0000 Message-ID: <53563ADF.9080707@lsces.co.uk> Date: Tue, 22 Apr 2014 10:48:15 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 SeaMonkey/2.24 MIME-Version: 1.0 To: internals@lists.php.net References: <52FF3BB7.8030408@lsces.co.uk> <52FF465E.4040400@lsces.co.uk> <5355A48D.7050600@sugarcrm.com> <53562CD0.5070006@sugarcrm.com> In-Reply-To: <53562CD0.5070006@sugarcrm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] utf-8 filenames in phar files. From: lester@lsces.co.uk (Lester Caine) Stas Malyshev wrote: > I'm sure these are serious issues, but I'm not sure - how do they relate > to the phar fix we're talking about? There is no logical reason to allow invalid UTF-8 data to be stored, so step one has to be to prevent it's use ... at least then one does not have to discuss just what happens to invalid data ... it's an error. -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk