Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35971
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 62.75.137.136 as permitted sender)
To: internals@lists.php.net,
 RQuadling@googlemail.com
Date: Wed, 5 Mar 2008 13:06:15 +0100
User-Agent: KMail/1.9.7
References: <10845a340803050221p5ca210a4mde18021d28e8e848@mail.gmail.com>
In-Reply-To: <10845a340803050221p5ca210a4mde18021d28e8e848@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-ID: <200803051306.16131.et@php.net>
Subject: Re: [PHP-DEV] PHP5.3.0-dev and Unicode BOM.
From: et@php.net (Stefan Walk)

On Wednesday 05 March 2008 11:21:14 Richard Quadling wrote:
> But, having just inherited a load of code which are UTF-8 encoded and
> all have a BOM marker, all the BOM markers are being sent to the
> browser. This screws up sessions as output is sent before headers
> (obviously).
>
> The files are english/non english mix, so I'm assuming the BOM needs
> to be present to indicate the order of the encoding (I'm new to the
> Unicode stuff, so this is my first real work with anything other than
> pure english PHP code). Because of this assumption, I think I can't
> remove the BOM marker.

Since the codeunits for UTF-8 are only one Byte long, the BOM is unnecessary. 
It's just added from some editors that use it as a marker "This file is 
UTF-8". So, you can safely remove it.

Additionally, i don't think PHP has ignored the BOM before.

Regards,
Stefan