Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93849
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 217.147.176.214 cause and error)
To: internals@lists.php.net
References: <CALYT1Yo97rG=onQPoVC8Mt9qhScdDfk9KYuKAmKyzK=7U3TfcA@mail.gmail.com>
 <e21002a7-5d21-212c-e344-2ea545bc5c3b@gmail.com>
 <CAESVnVrx6MwE0dktVDgSt6B+cTtOTTS_qeE4CwqFbTKKUEuqNw@mail.gmail.com>
 <7b80be21-b397-c40c-8e80-ff4da4f97634@gmail.com>
 <CALYT1Yqs7ekyeohgT4wNDCrHz43J6FpJ5=+UEdiGZjZY28Z+ow@mail.gmail.com>
Message-ID: <5755F534.4010903@lsces.co.uk>
Date: Mon, 6 Jun 2016 23:12:04 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <CALYT1Yqs7ekyeohgT4wNDCrHz43J6FpJ5=+UEdiGZjZY28Z+ow@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP's handling of BOM (byte order mark)
From: lester@lsces.co.uk (Lester Caine)

On 06/06/16 22:33, Sammy Kaye Powers wrote:
> But the real hum-dinger was from Stack Overflow:
> 
> http://stackoverflow.com/search?q=php+bom
> 
> It does seem to be tripping up a lot of people, especially newbies. As
> low as the learning curve is for PHP already, I'm curious if you folks
> think it's advantageous to have PHP ignore the BOM in std out in the
> case of `{U+FEFF}<?php` to remove another stumbling block.

BUT is this actually anything to do with BOM?
From stackoverflow
http://stackoverflow.com/questions/35549518/php-import-csv-file-utf8-with-bom
Check the answer.

I'm not saying PHP handles UTF8 properly, but most of the problems tend
to be more to do with the source file encoding rather than PHP? The
majority of the answers even from years back are 'don't use BOM' but I
am curious where the \u{feff} comes from in your original post since the
UTF8 BOM is \u{efbbbf} and anything else should be stripped. The
starting point should perhaps be http://unicode.org/faq/utf_bom.html
which acknowledges that it's use can be a problem and specifically ...

Some byte oriented protocols expect ASCII characters at the beginning of
a file. If UTF-8 is used with these protocols, use of the BOM as
encoding form signature should be avoided.

Which is where the advise not to use them comes from ...

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk