Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:17809 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72043 invoked by uid 1010); 10 Aug 2005 20:17:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 72028 invoked from network); 10 Aug 2005 20:17:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Aug 2005 20:17:17 -0000 X-Host-Fingerprint: 216.145.54.171 mrout1.yahoo.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([216.145.54.171:25495] helo=mrout1.yahoo.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id E0/C3-24081-CC06AF24 for ; Wed, 10 Aug 2005 16:17:16 -0400 Received: from [66.228.175.145] (borndress-lm.corp.yahoo.com [66.228.175.145]) by mrout1.yahoo.com (8.13.4/8.13.4/y.out) with ESMTP id j7AKFUEe017364; Wed, 10 Aug 2005 13:15:31 -0700 (PDT) In-Reply-To: <20050810145407.3917271d.antony@zend.com> References: <937066F0-AA5F-41E2-99A0-D74C7F44FFCA@gravitonic.com> <1B.49.24081.1DAD9F24@pb1.pair.com> <20050810145407.3917271d.antony@zend.com> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-ID: <186a325473127b5a6e32111cc292999b@gravitonic.com> Content-Transfer-Encoding: 7bit Cc: "Ron Korving" , internals@lists.php.net Date: Wed, 10 Aug 2005 13:15:28 -0700 To: Antony Dovgal X-Mailer: Apple Mail (2.622) Subject: Re: [PHP-DEV] Re: PHP Unicode support design document From: andrei@gravitonic.com (Andrei Zmievski) On Aug 10, 2005, at 3:54 AM, Antony Dovgal wrote: > Do we really need such kind of magic? > > I think it may be pretty confusing when after echo'ing or print'ing a > variable > you can see one output, but after writing the very same variable into > a file > you can see something completely different. Absolutely, we do need it. Consider that the internal encoding is UTF-16 and outputting that directly to a terminal (or browser) is bound to cause havoc. That's just one of the examples. -Andrei