Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58856 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16374 invoked from network); 12 Mar 2012 07:10:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Mar 2012 07:10:15 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 207.97.245.113 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 207.97.245.113 smtp113.iad.emailsrvr.com Linux 2.6 Received: from [207.97.245.113] ([207.97.245.113:32975] helo=smtp113.iad.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 04/E2-33887-651AD5F4 for ; Mon, 12 Mar 2012 02:10:14 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp31.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id E2D903E051B; Mon, 12 Mar 2012 03:10:11 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp31.relay.iad1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 806323E051C; Mon, 12 Mar 2012 03:10:11 -0400 (EDT) Message-ID: <4F5DA152.10109@sugarcrm.com> Date: Mon, 12 Mar 2012 00:10:10 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: Rasmus Lerdorf CC: PHP internals References: <4F5D9C77.3030000@lerdorf.com> In-Reply-To: <4F5D9C77.3030000@lerdorf.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] default charset confusion From: smalyshev@sugarcrm.com (Stas Malyshev) 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 INIs 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 UTF-8 are 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 little sense out of it, it lacks expected result and I have hard time understanding what is the problem there. Could you explain? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227