Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58858 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22175 invoked from network); 12 Mar 2012 07:36:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Mar 2012 07:36:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.170 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.217.170 mail-lb0-f170.google.com Received: from [209.85.217.170] ([209.85.217.170:46074] helo=mail-lb0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 28/50-20445-B77AD5F4 for ; Mon, 12 Mar 2012 02:36:28 -0500 Received: by lbbgg13 with SMTP id gg13so945979lbb.29 for ; Mon, 12 Mar 2012 00:36:24 -0700 (PDT) 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 :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=f1Xy5KP5dVkocjAnKWR7UWbgq00wTZ9KT5ivbxFRy2E=; b=vniEAp5OG1o771R3ASwzDwGpnnYTO5fWYeHIiB1XfB0WSQZbbFsMxJcG50H/pYAynk Eo3+A2PQjzf0ntso2tYZ4sBi8ZVNUpQHvHJvrW/sqWxXYpa119BqSjLEmr/LJbbnS6jB w6SVoqBUSeosXRMYz4SLzI4cThM52NUOMobZBHjL+abyBwnLIJH/XSf5Nh4aq2oWcKvQ M9k06LUQXChHz225KZtp1vdv6jVZCh6lkRLviY/AJQfFCto1evpWuyDDS3zhqIydzSxs toIqQOjc8iKpDyw/uGqf7/vHIznVSc6/wjVl56tgGG7zH1bOeuOnIRqmscnxl4nDPpha avYw== Received: by 10.112.48.130 with SMTP id l2mr4315327lbn.41.1331537784245; Mon, 12 Mar 2012 00:36:24 -0700 (PDT) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.112.20.73 with HTTP; Mon, 12 Mar 2012 00:36:04 -0700 (PDT) In-Reply-To: <4F5DA152.10109@sugarcrm.com> References: <4F5D9C77.3030000@lerdorf.com> <4F5DA152.10109@sugarcrm.com> Date: Mon, 12 Mar 2012 15:36:04 +0800 X-Google-Sender-Auth: rKMOLdw7JWpiyKR4_-OtKeZTclc Message-ID: To: Stas Malyshev Cc: Rasmus Lerdorf , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] default charset confusion From: laruence@php.net (Laruence) On Mon, Mar 12, 2012 at 3:10 PM, Stas Malyshev wro= te: > Hi! > > >> What we really need is what we added in PHP 6. A runtime encoding ini >> setting that is distinct from the output charset which we can use here. >> That would allow people to fix all their legacy code to a specific >> runtime encoding with a single ini setting instead of changing thousands >> of lines of code. I propose that we add such a directive to 5.4.1 to >> ease migration. > > > One more charset INI setting? I'm not sure I like this. We have tons of I= NIs If we will definitely add a run_time_charset in the furture, then I think it's okey add it now. :) thanks > already, and adding a new one each time we change something makes both > writing applications and configuring servers harder. > But as the manual says, ISO-8859-1 and =C2=A0UTF-8 =C2=A0are the same for > htmlspecialchars() - is it wrong? If yes, what exactly is the different > between old and new behavior? I tried to read #61354 but could make littl= e > sense out of it, it lacks expected result and I have hard time understand= ing > what is the problem there. Could you explain? > > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > --=20 Laruence =C2=A0Xinchen Hui http://www.laruence.com/