Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72728 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70091 invoked from network); 21 Feb 2014 02:59:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Feb 2014 02:59:04 -0000 Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.46 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.46 mail-qg0-f46.google.com Received: from [209.85.192.46] ([209.85.192.46:50159] helo=mail-qg0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/D3-49610-7F0C6035 for ; Thu, 20 Feb 2014 21:59:03 -0500 Received: by mail-qg0-f46.google.com with SMTP id e89so6116902qgf.5 for ; Thu, 20 Feb 2014 18:59:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wd21D/EknTpvGKHamFxJ0VXCI5gYWGnRZEjNCSpxadg=; b=DOsJT2I9hfpw8s+CnUy8XVWter8WGTPuW9u4U9FB8Z5ENtWPVIOEJZUXMrwX5KjYEn e1ArwzglaWwXXvTY/5V/trk/9l5qd7flhF+PoHCJLk+vUzYE8Q8cy9y9PF10oOj8buZp rSQ6aKD8k4r1UEWUEVRwQBWyq8YoF7b0KpBNkYt73ViAnzyyAP7yVrtKWju1LB2ZtdRz 03l7k4Ikztem4RNDc7DUtNeKvzh/F45AarkvGI6KjLDVpo+ayBZHFKsrJ94pfU6UTYAn l+8tPw5OOkhWNBSXjWc34Mk4XZhSETvl4oSaWnjHR+5l/g6DWsD1hD1oYNCXZFIaGGy8 JMAQ== MIME-Version: 1.0 X-Received: by 10.224.104.9 with SMTP id m9mr6536375qao.18.1392951540527; Thu, 20 Feb 2014 18:59:00 -0800 (PST) Received: by 10.140.18.145 with HTTP; Thu, 20 Feb 2014 18:58:59 -0800 (PST) Received: by 10.140.18.145 with HTTP; Thu, 20 Feb 2014 18:58:59 -0800 (PST) In-Reply-To: <53066DE9.4090809@googlemail.com> References: <53061982.2050901@googlemail.com> <53066DE9.4090809@googlemail.com> Date: Fri, 21 Feb 2014 03:58:59 +0100 Message-ID: To: Crypto Compress Cc: PHP internals Content-Type: multipart/alternative; boundary=001a11c1bd70c335b604f2e1cdbb Subject: Re: [PHP-DEV] [php6] Unicode support, options? From: pierre.php@gmail.com (Pierre Joye) --001a11c1bd70c335b604f2e1cdbb Content-Type: text/plain; charset=UTF-8 On Feb 21, 2014 4:05 AM, "Crypto Compress" wrote: > > Hi Pierre, > >> >> Thoughts, comments or ideas? >> > >> > it may be crazy to even think about it, but my idea is to mix the "worst" (C++ *and* ICU) to get the ultimate unicode foundation. >> > >> > Boost.Locale: >> > http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/rationale.html#why_icu >> >> Mainly because we like to use UTF-8 storage. >> > > What do you understand by "storage"? To have string stored as UTF-8 only, no conversion required for 99% of our use. > Quote: "U_CHARSET_IS_UTF8 allows to force ICU to use UTF-8 by default. It is a ICU compile time setting." > Source: Pierre > > Quote: "...stateless encodings like UTF-8..." > Source: http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/charset_handling.html#codecvt_limitations ICU has limitations in the utf-8 mode. To bundle UTF-8 or ask custom build could be a problem as well. The other point to check is whether ICU can have two installs on the sane systems, one with the flag and one without. It could help as distros can then provide both. > >> Also pure c++ api is not an option yet. Unless we rewrite php in c++ but then I would go with a 3-4 years Dev phase >> > > Yes, a complete rewrite is insane not crazy. Prefer small evolutionary steps and some bigger ones. > >> ...not really what I am looking for. >> > > We know what you are looking for. You asked for ideas. Maybe I was not clear here. What I am not looking for is to delay a possible 6 release to 2-3 years later. Ideas, like yours here, are indeed more than welcome. --001a11c1bd70c335b604f2e1cdbb--