Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71211 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35897 invoked from network); 17 Jan 2014 20:07:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Jan 2014 20:07:22 -0000 Authentication-Results: pb1.pair.com header.from=julienpauli@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=julienpauli@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.45 as permitted sender) X-PHP-List-Original-Sender: julienpauli@gmail.com X-Host-Fingerprint: 209.85.219.45 mail-oa0-f45.google.com Received: from [209.85.219.45] ([209.85.219.45:48179] helo=mail-oa0-f45.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9A/D2-16023-97D89D25 for ; Fri, 17 Jan 2014 15:07:21 -0500 Received: by mail-oa0-f45.google.com with SMTP id i11so278472oag.32 for ; Fri, 17 Jan 2014 12:07:18 -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=oiOB0dMkkgJuG9Qty7la4lAXFqUHTgFqF83ey/3cA74=; b=OzLguG1tIx7cgUdmp+FeVThDce8dvLenPlrXr5jVBdgflx0vE2xCJPrT9nZgBVdcAU jloHzg1q0IeuJ6NI8sSdWxUFQLUHfMHbWZNYChIbyBIykPOqNiVww95Lwm2a/z5Us4Bo huZpV3bgZhSyT7nDxTq4Hn4NXy4as5BlRJxGxGCF/7nyiYSH5ZKH/Bqhp+IC2e9CsSEA LOLNpGBhzlcGzGz1EdOhi+zKgp97unYD3MXSEAt/Qrw6dTSy35WWk2B89NLZVKhTFwXy DgKF6+kQMjxIZDMsAORopcclABUaTfNQlqR9OOfnJxVqdnpGTKg5z97OhQ1BtjAoDmmV HFJA== X-Received: by 10.60.34.3 with SMTP id v3mr3040410oei.67.1389989238370; Fri, 17 Jan 2014 12:07:18 -0800 (PST) MIME-Version: 1.0 Sender: julienpauli@gmail.com Received: by 10.182.235.46 with HTTP; Fri, 17 Jan 2014 12:06:38 -0800 (PST) In-Reply-To: <1389976678.2057.8.camel@smugmug> References: <1389976678.2057.8.camel@smugmug> Date: Fri, 17 Jan 2014 21:06:38 +0100 X-Google-Sender-Auth: 9dwTpw7NDVqJRELPQ2dPPuifZuI Message-ID: To: Mike Cc: Yasuo Ohgaki , Nikita Popov , "internals@lists.php.net" Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] [RFC] Multibyte char handling From: jpauli@php.net (Julien Pauli) [Sorry I cant answer inline as there are many answers to give to many users] Like everybody, I' absolutely against adding an "encoding" parameter to ext/standard functions or relying on unreliable system locale. Like Nikita says, every multibyte function should go to ext/mbstring , and nowhere else, please , do not turn PHP into something even more dirty as it is nowadays :-p I'm +1 to embed and activate mbstring by default in future PHP releases. However, this has already been discussed (from what I remember) and I dont remember why we ended with a "no" end-word, could we be refreshed about this ? I'm not in favor of magic things. Magically replacing PHP strings by mb_ implementation is a really bad idea. We should keep the INI parameter about this alive though (mbstring.func_overload), so that people that explicitely want to activate such a magic can do it if they want to. I'm +1 also to start a "serious" (hum) discussion about multibyte/PHP6 , we've been saying this for years : we need native support of unicode in PHP :-p The actual problem we are facing once again shows this. Julien.P