Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73758 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21602 invoked from network); 21 Apr 2014 23:06:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Apr 2014 23:06:59 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.75 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.75 smtp75.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.75] ([108.166.43.75:56571] helo=smtp75.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 0D/B9-00448-194A5535 for ; Mon, 21 Apr 2014 19:06:58 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp2.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 716EC1E8556; Mon, 21 Apr 2014 19:06:54 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp2.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id CB28A1E8B22; Mon, 21 Apr 2014 19:06:53 -0400 (EDT) Message-ID: <5355A48D.7050600@sugarcrm.com> Date: Mon, 21 Apr 2014 16:06:53 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Jakub Zelenka , Yasuo Ohgaki CC: Lester Caine , PHP internals References: <52FF3BB7.8030408@lsces.co.uk> <52FF465E.4040400@lsces.co.uk> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] utf-8 filenames in phar files. From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I have created a quick PR: https://github.com/php/php-src/pull/649 that > is fixing the ill-formed UTF-8 paths. Thanks for the patch. One thing I'd like to understand is what is the added value of being so strict in checking UTF-8. I.e. what would happen if we allow some path with weird chars in? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227