Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23428 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56628 invoked by uid 1010); 15 May 2006 21:53:44 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 56613 invoked from network); 15 May 2006 21:53:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 May 2006 21:53:44 -0000 X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:59527] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 35/65-19568-768F8644 for ; Mon, 15 May 2006 17:53:44 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k4FLrcnV015571; Mon, 15 May 2006 23:53:38 +0200 Date: Mon, 15 May 2006 23:53:25 +0200 (CEST) X-X-Sender: derick@localhost To: Nuno Lopes cc: Andrei Zmievski , PHPdev In-Reply-To: <003a01c67869$160f52c0$0100a8c0@pc07653> Message-ID: References: <003d01c672ef$6cde8370$0100a8c0@pc07653> <517361123ef66114064e2866c95e3caa@gravitonic.com> <000901c67857$c20fa190$0100a8c0@pc07653> <7abd987289270ef00178d1bbf8e32c0b@gravitonic.com> <002401c67866$d1497f50$0100a8c0@pc07653> <9c2e6ce480a09868788a4a4a46523235@gravitonic.com> <003a01c67869$160f52c0$0100a8c0@pc07653> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] [php6] accepting an ascii string only From: derick@php.net (Derick Rethans) On Mon, 15 May 2006, Nuno Lopes wrote: > I was not refering to the html/xhtml/xml input. I was talking about the > charset parameter, for example. I don't want a chinese string passed as the > charset name (the libtidy API isn't localized yet :) ). The same applies for > the other functions. Yeah, but that doesnt mean you need to throw a hard error on passing a unicode string here. They can also contain just ascii data which is perfectly acceptable. regards, Derick