Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73790 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62007 invoked from network); 25 Apr 2014 01:44:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Apr 2014 01:44:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.180 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.217.180 mail-lb0-f180.google.com Received: from [209.85.217.180] ([209.85.217.180:54987] helo=mail-lb0-f180.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 01/00-61928-2EDB9535 for ; Thu, 24 Apr 2014 21:44:03 -0400 Received: by mail-lb0-f180.google.com with SMTP id 10so2556050lbg.39 for ; Thu, 24 Apr 2014 18:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=U2SaUTYNTkgKgokhy3ux8jkAuhx0kUykHYOBV2b2K1g=; b=lJSTsk9ZGCWp0SbcqL06hCqSEsrsvFlGZ/hM+GdHDUgaOWVcsk7mujtExotb3VhpLn GKyMnyTw4H9+pY37RBEVs6d8f4n4KrjmHa2D54WYhyAZ1DJWSLHBotMhhNkmJX/Clb3j yujnL385aCZcgxLrze+G60h1CmiAbDv6GJvT3ML8vWMpLo2A/cHwKYX8Zh2UsueZk4fY MU9iksMRexzuPOCWTl1kvWvIAnFTsi15F9iGx4QZZ0vXSMy1d5PCgpNrrJXQ2KqLrBmF aqoL5CMHn1BfobZ+c5snd6Hl2u15SHI1aCsI9RpGKFW5fyaiD/GOzFWH+kCLh/faFExR QlUw== X-Received: by 10.153.4.134 with SMTP id ce6mr3397451lad.21.1398390240089; Thu, 24 Apr 2014 18:44:00 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.205.73 with HTTP; Thu, 24 Apr 2014 18:43:20 -0700 (PDT) In-Reply-To: <53561D4E.6000609@lsces.co.uk> References: <52FF3BB7.8030408@lsces.co.uk> <52FF465E.4040400@lsces.co.uk> <5355A48D.7050600@sugarcrm.com> <53561D4E.6000609@lsces.co.uk> Date: Fri, 25 Apr 2014 10:43:20 +0900 X-Google-Sender-Auth: FcFharTEFyFP5t9ZTxnf0mZxpAA Message-ID: To: Lester Caine Cc: "internals@lists.php.net >> PHP internals" Content-Type: multipart/alternative; boundary=001a1134de96849a2304f7d4190f Subject: Re: [PHP-DEV] utf-8 filenames in phar files. From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a1134de96849a2304f7d4190f Content-Type: text/plain; charset=UTF-8 Hi Lester, On Tue, Apr 22, 2014 at 4:42 PM, Lester Caine wrote: > Yasuo Ohgaki wrote: > >> BTW, without NFC normalization, I sure there will be unhappy users if >> users use >> it with >> OSX and Linux/Windows. OSX decomposes Unicode and there will be the same >> name >> path with different unicode string that appears the same on their >> terminal/etc >> on Linux/Windows. >> > > I don't think this problem is any different to the simple conflict between > upper and lower case 'normalizing' that happens currently? Each OS has it's > own standards and quirks which we have to put up with. It is a simple fact > that UTF-8 does NOT have a preferred standard, and everything that is valid > has to be handled. This is back to the question on case insensitive > comparisons, and if even that can be supported going forward. If different > OS's 'normalise' a string for their own purposes can we be expected to > provide different comparison rules for each? Or is it something that has to > be passed back up the chain for a library to handle more generically? > > Phar should not 'translate' anything ... it is where these strings are > used that should handle any additional processing? Phar could be extracted. Path name composition is mandatory for compatibility between OSX and Linux/Windows, since OSX decomposes path name intentionally. If you are curious, research how git works with OSX. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a1134de96849a2304f7d4190f--