Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49181
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        b=td5N2P/WadyVqWmfmFlef/IrvwDp/0yN4/bJiyBa6bBoB4CAgqTB0fCgp6SMAIP7H+
         drmJH0vWWPZQcItT0urlUBT2jg6L13VrMLqH+hPDJ5ohfK2LQK0MQ8jI7yDXa2vdy7KQ
         OvjINQpy6dcGDEdXZYAR4t+63Q10n81ff+FY8=
MIME-Version: 1.0
Sender: tyra3l@gmail.com
In-Reply-To: <1280443768.10693.13.camel@guybrush>
References: <AANLkTin8n1Fo-ORfumyj+JzSyAAKoU39ZTjhmjcnwuKu@mail.gmail.com>
	<1280440681.10693.5.camel@guybrush>
	<AANLkTi=kr_mtWZrDya2BVc2NZxSYXEr5-e=NTerwQXQ9@mail.gmail.com>
	<1280443768.10693.13.camel@guybrush>
Date: Fri, 30 Jul 2010 00:54:31 +0200
Message-ID: <AANLkTi=DT+uQXs0TwAC4C3Tb+cfQvXaRhzP+zwzFAEVa@mail.gmail.com>
To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] --enable-zend-multibyte
From: info@tyrael.hu (Ferenc Kovacs)

2010/7/30 Johannes Schl=C3=BCter <johannes@schlueters.de>:
> Hi,
>
> On Fri, 2010-07-30 at 00:33 +0200, Ferenc Kovacs wrote:
>> > Ignoring the BOF might cause not expected behavior: Assume people are
>> > using PHP as "templating" language and want the BOM to go out to the
>> > client.
>
>> Do you think that this is a common scenario?
>> Apart from a case, when I had to create utf-8 csv files for Microsoft
>> Excel, I never needed to send BOM from php, and for that particular
>> case, I sent it with an explicit echo, not with an "invisible" control
>> sequence in my code.
>
> Well, PHP doesn't change what is written outside <?php ?> (*) so hiding
> "random" bytes (PHP doesn't know what these bytes mean, PHP only knows
> collections of bytes as strings with no further logic) might easily
> break expectations and cause problems which are harder to trace down
> than a "headers already sent" error which is relatively verbose.
>
> johannes
>
> *) Yes there is one behavior which might be seen as an exception: If ?>
> is directly followed by a new line the new line is dropped, but then the
> new line can be seen part of the ?>.
>
> Example:
>
> a<?php
> ?>
> b
>
> Prints
>
> ab
>
> without line break.
>
>

I see your point.

I can not come up anything better than your first idea.

Tyrael