Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71312 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 33273 invoked from network); 20 Jan 2014 08:58:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Jan 2014 08:58:33 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; 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:55535] helo=mail-la0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BF/76-02192-735ECD25 for ; Mon, 20 Jan 2014 03:58:32 -0500 Received: by mail-la0-f54.google.com with SMTP id y1so5340936lam.13 for ; Mon, 20 Jan 2014 00:58:28 -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=/njxZpHEEanMycY3q+8G2Cb+dK5AItlyUzZOGhDFRqk=; b=NdvJ7gX5/Buy/nxYzeCOEr1Dgn0U7BFbVv386qLSGQSPSSq8EZlngdj/vEplIAzre8 OrHR++H+PfAr7PE0cvWrC2WiuYcHyUIZrGQLC27VxOnCSy8zjNShfl8hGV++b4fwE2ke h3AO81mKHhWBPAacV1ku78b7OpX1iZjX1BTwFg15eEjiyeD3xSbe2KuzZnoeoTIYV9LG mifCZesyzAka1qIhEhuNyKzY2DV2MTPtgCCPcPGBw30TmpTXrr3HmetcRpnbnXJqQQlK 6hPhsNoqLoEXhQVZt9ul9gGl0nhy0hM55zX4K4gtYrV3aX3SakkepX6AseL++5+27Rpm Z61w== X-Received: by 10.152.5.199 with SMTP id u7mr360884lau.48.1390208308494; Mon, 20 Jan 2014 00:58:28 -0800 (PST) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.112.6.68 with HTTP; Mon, 20 Jan 2014 00:57:48 -0800 (PST) In-Reply-To: References: Date: Mon, 20 Jan 2014 17:57:48 +0900 X-Google-Sender-Auth: sq5vkjLbAu1MbTfFxfx8zhxP98A Message-ID: To: Pierre Joye Cc: PHP internals , Nikita Popov Content-Type: multipart/alternative; boundary=089e013d1a7864468d04f06318d2 Subject: Re: [PHP-DEV] [RFC] Multibyte char handling From: yohgaki@ohgaki.net (Yasuo Ohgaki) --089e013d1a7864468d04f06318d2 Content-Type: text/plain; charset=UTF-8 Hi Pierre, On Mon, Jan 20, 2014 at 3:38 PM, Pierre Joye wrote: > > On UNIXes, UTF-8 encoding is popular terminal encoding, but there > > would be systems using other encoding such as EUC, or even SJIS, BIG5. > > Right, and as far as I remember UTF-8 does not suffer from this problem. > UTF-8 does not have this issue if terminal handles encoding correctly. I think almost all termianls handle UTF-8 properly, otherwise it is considered as security hole :) > > Windows uses different encoding for terminal encoding according to > locale, > > so it's much more complex. > > > > Let me provide a function to detect it, but we need something to normalize > the names. Do we have such thing in mbstring? > Yes. mbstring has ID for supported encoding and there is normalize function to set encoding ID. > > This is the reason why I would use locale. However, this implementation > > is debatable. > > > > Yes :) > We need to decide what to do :) Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --089e013d1a7864468d04f06318d2--