Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72606 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41410 invoked from network); 14 Feb 2014 16:39:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Feb 2014 16:39:54 -0000 Authentication-Results: pb1.pair.com header.from=rowan.collins@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=rowan.collins@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.171 as permitted sender) X-PHP-List-Original-Sender: rowan.collins@gmail.com X-Host-Fingerprint: 209.85.212.171 mail-wi0-f171.google.com Received: from [209.85.212.171] ([209.85.212.171:51886] helo=mail-wi0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 79/61-34645-7D64EF25 for ; Fri, 14 Feb 2014 11:39:53 -0500 Received: by mail-wi0-f171.google.com with SMTP id cc10so650809wib.16 for ; Fri, 14 Feb 2014 08:39:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=gNDe7/RrLV2EQZbzM8TGt2eUVTgVJoI9GkVTyrZCG/Q=; b=0ve6dxSHSQLg3QSMRiiM8ZwMNp+aykM4ZI4RIQiqvTSKTWpy2DvbnkK8HQtur0Zin3 bolvc0gLnL2L98rGhcfPA3yBNDtqGlbDAT6LQpSQyJE2xnHihXhjznN8MjzjRcfzt+gJ 6tz2+JErIsA0cTDnhq4EBNVyTEGUqEQd3cw5g+j/E9leMiSqhL1JzphJO9QyCD0D2ziJ 15uwnNywyJagylB0bmx3+EJnw4eipHcJet6GLMzvBMV6hdTKP+9ET9skhziJ62Ri1fCi wykQRXRH2N69u856eZCIU6suTyRYGcOWpcSUhpzUvQCTn5bQa1u2m7hj6S+lzthR9M0i 5+sw== X-Received: by 10.180.100.72 with SMTP id ew8mr3125769wib.16.1392395989170; Fri, 14 Feb 2014 08:39:49 -0800 (PST) Received: from [192.168.0.150] ([62.189.198.114]) by mx.google.com with ESMTPSA id j9sm13893112wjz.13.2014.02.14.08.39.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Feb 2014 08:39:48 -0800 (PST) Message-ID: <52FE46D2.4060903@gmail.com> Date: Fri, 14 Feb 2014 16:39:46 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: internals@lists.php.net References: <50100EC8.3040102@ajf.me> <52FDF7BC.8050408@lsces.co.uk> In-Reply-To: <52FDF7BC.8050408@lsces.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] PHP6 wiki page From: rowan.collins@gmail.com (Rowan Collins) Lester Caine wrote (on 14/02/2014): > But more fundamentally I don't think there was agreement on whether we > simply standardise on unicode in the core, or allow a single byte > mode? 8 years on, I feel that the amount of utf8 material that is > floating around, the easiest route IS unicode only? The question is not whether to be "Unicode only", it's *how* to implement Unicode. It's not just a case of making all your strings wider, every function that manipulates a string in any way has to be thought through, and every input and output has to be converted to/from whatever encoding is chosen as the internal implementation. While updating the Wikipedia article [1] I came across this slide set [2], which has a fairly decent explanation of the issues and why the previous implementation was abandoned. If somebody comes up with an implementation proposal of Unicode strings, whether to have a mode that doesn't use it can be discussed, but right now there doesn't seem to be such a live proposal. [1] http://en.wikipedia.org/wiki/PHP#PHP_6_and_Unicode [2] http://www.slideshare.net/andreizm/the-good-the-bad-and-the-ugly-what-happened-to-unicode-and-php-6 Regards, -- Rowan Collins [IMSoP]