Guy<p>Argh!!!</p><p>Classic <a href="https://mastodon.nz/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> fail move. Exporting an <a href="https://mastodon.nz/tags/Excel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Excel</span></a> 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).</p><p>Unfortunately the Unicode spec clearly discourages this strongly:</p><p>> 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</p><p>Why does this evil empire have to make everything unnecessarily difficult???</p><p><a href="https://mastodon.nz/tags/fail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fail</span></a></p>