Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:48179 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42621 invoked from network); 3 May 2010 15:44:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 May 2010 15:44:07 -0000 Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 188.40.37.16 hq1.backendmedia.com Linux 2.6 Received: from [188.40.37.16] ([188.40.37.16:34858] helo=hq1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C5/46-09795-64FEEDB4 for ; Mon, 03 May 2010 11:44:07 -0400 Received: from localhost (unknown [127.0.0.1]) by hq1.backendmedia.com (Postfix) with ESMTP id 68FC1200C19A; Mon, 3 May 2010 15:44:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from hq1.backendmedia.com ([127.0.0.1]) by localhost (hq1.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KoDIJtgb3gQH; Mon, 3 May 2010 17:44:01 +0200 (CEST) Received: from [192.168.80.107] (77-58-249-88.dclient.hispeed.ch [77.58.249.88]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by hq1.backendmedia.com (Postfix) with ESMTPSA id 9392A200C18A; Mon, 3 May 2010 17:44:01 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii In-Reply-To: <4BDE0259.3090904@moonspot.net> Date: Mon, 3 May 2010 17:44:00 +0200 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <4BDE0259.3090904@moonspot.net> To: Brian Moon X-Mailer: Apple Mail (2.1078) Subject: Re: [PHP-DEV] Using default_charset for htmlspecialchars() and others From: mls@pooteeweet.org (Lukas Kahwe Smith) On 03.05.2010, at 00:53, Brian Moon wrote: > I am not sure if this has been discussed or not. I will gladly make an = RFC if not. I think it would be very intuitive if htmlspecialchars used = the ini value default_charset as its default. And any function that = takes an optional character set. >=20 > A) Has this been discussed? > B) If not, do others think it is worth of a proper RFC? >=20 > There would be some BC breakage for sure as the default behavior would = be changing. Due to this BC and the fact that I do not see this as a super pressing = issue, I would hold off with doing this change until we have our unicode = plans more concrete, because this might result in yet another change in = this area. regards, Lukas Kahwe Smith mls@pooteeweet.org PS: Then again .. the entire unicode discussion seems to have died on = this list and I am not aware of any documentation having been made or = any other tangible progress.