Toxic byte order markers at beginnings of files lead to rendering errors

So, this one took me a really long time to track down, but I recently upgraded google_plusone to the 7.x-1.x-dev version, which had the side effect of causing several insidious problems, but the main one being that a byte order marker (bom) was being put on pages before output. This was at its worst when delivering json content using the services module, because the BOM was getting output at the beginning of the string.

These markers don't render in many editors or browsers, though you may see gibberish such as 
In less the character would show as U+FEFF

I found these by using the advice here: http://stackoverflow.com/questions/204765/elegant-way-to-search-for-utf-...

grep -rl $'\xEF\xBB\xBF' .

This showed the culprits were two files google_plusone_badge.admin.js and google_plusone.module, both at the beginning of the file.

A diff is attached, or you can use find . -type f -exec sed '1s/^\xEF\xBB\xBF//' -i.bak {} \; -exec rm {}.bak \;