Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72626 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 54216 invoked from network); 15 Feb 2014 10:54:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Feb 2014 10:54:22 -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.215.54 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.215.54 mail-la0-f54.google.com Received: from [209.85.215.54] ([209.85.215.54:40489] helo=mail-la0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FD/21-45929-C574FF25 for ; Sat, 15 Feb 2014 05:54:21 -0500 Received: by mail-la0-f54.google.com with SMTP id y1so10109832lam.13 for ; Sat, 15 Feb 2014 02:54:17 -0800 (PST) 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=8HZUyQcEoiSQMHVL3KTI085KiW7tmgt+eYBMyB9IURU=; b=LDvFQkdF9eCj8X67WZv2wVBXMcl7lr47I5OBGr7Hgm0ytdkfo4o0q0KZOEv891JotA p61qHzgCKBVbuCE3rB8XpXk9ypZ3kczCBpQhLQEFOpTJzOzmTmGsB0OgvkxToJ+jtOIg iKztSaAaoB9b2Eo5i/sHbtcxHZk3gyZ2IZ3+IFpcDYRiRvuMDpd0bV3mPvXRvghbYWUL ac7Db8a9cUZZy8F2cJ5rpncwhuZEWBeLAg7gilr4fQs+AKQDuNuI1PwmImxEtFoSRfP+ ajwgblNjbmDlPuX6qLdxKI3ys8ig0RgyVwj9ilOHQLKms3Q1mNuZW0xRKgqjRjcRcg8C U9WA== X-Received: by 10.152.190.69 with SMTP id go5mr98511lac.79.1392461657622; Sat, 15 Feb 2014 02:54:17 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.199.37 with HTTP; Sat, 15 Feb 2014 02:53:37 -0800 (PST) In-Reply-To: <52FF465E.4040400@lsces.co.uk> References: <52FF3BB7.8030408@lsces.co.uk> <52FF465E.4040400@lsces.co.uk> Date: Sat, 15 Feb 2014 19:53:37 +0900 X-Google-Sender-Auth: lEMoxeDLk0lSyUeNJA-cCDlUZY8 Message-ID: To: Lester Caine Cc: PHP internals Content-Type: multipart/alternative; boundary=001a1136c86c774cbe04f26fbee6 Subject: Re: [PHP-DEV] utf-8 filenames in phar files. From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a1136c86c774cbe04f26fbee6 Content-Type: text/plain; charset=UTF-8 On Sat, Feb 15, 2014 at 7:50 PM, Lester Caine wrote: > My previous post did not appear on the list ;) > > > Yasuo Ohgaki wrote: > >> A lot of the current confusion does seem to be based around the >> Windows >> Wide-API as documented in 'The Problem' section of that document. It >> would >> seem that my 'naive' view of simply using UTF-8 strings is thwarted >> by these >> problems?-- >> >> Unicode is like one name with several encoding. We cannot get away from >> conversions, normalization especially. >> > > That is why personally I'm just looking at UTF8. Which is enough of a mine > field on it's own, but since a large swath of what we are working with now > is only UTF8 it does seem to be the right base going forward? > I have problem, too. It seems someone is working on DKIM. Anyway, there are problems, but UTF-8 is way to go. We just cannot remove conversions. Normalization has number of issues, including security related one. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a1136c86c774cbe04f26fbee6--