Argh!!!
Classic #Microsoft fail move. Exporting an #Excel spreadsheet to CSV (for further processing later via Python scripts), I've found a niggling `\ufeff` character leading it off, which has bombed my pipelines. It looks like this zero-width, non-breaking space is used as a BOM (byte order mark) by Excel (though explicitly exporting to UTF-8).
Unfortunately the Unicode spec clearly discourages this strongly:
> The serialized order of the bytes must not depart from the order defined by the UTF-8 encoding form. Use of a BOM is neither required nor recommended for UTF-8
Why does this evil empire have to make everything unnecessarily difficult???