# Ignore UTF-8 BOM with csvsimple?

I am currently using csvsimple to include some external data in a document processed with pdfLaTeX. The entire project uses UTF-8 as encoding. The original data is maintained in an Excel 2010 file, and since Excel does not support exporting to UTF-8 CSV directly, I have to go through a rather cumbersome process:

• export to CSV
• save from notepad, changing the encoding

This process adds a BOM to the CSV file - 0xef 0xbb 0xbf. On my Windows desktop, this does not seem to be a problem, but the CI build on a Linux box breaks down with Missing \endcsname inserted.. Is there a way to tell csvsimple to ignore the BOM or do I have to edit it out before the compilation starts?

• Several editors don't add a BOM, which seems to be characteristic with Notepad. There are utilities that change the encoding without the need of opening an editor (and don't add the BOM) like Charco but there are surely several others. I'm quite surprised that a well known application doesn't allow exporting as UTF-8 in 2014 (29 years after its first release). – egreg Oct 31 '14 at 9:13
• @egreg You're right, but I was equally surprised that a well known (text) file processing software is unable to handle BOMs in the input :-) – vwegert Oct 31 '14 at 9:19
• TeX predates UTF-8 by several years. Maybe this could be a feature request for the next release of TeX Live. – egreg Oct 31 '14 at 9:23
• Is using another editor than Notepad an option? Notepad++ e.g. allows to save without BOM. – Thomas F. Sturm Oct 31 '14 at 9:36
• Do you use Notepad or Notepad++? With Notepad++ you can configure the encoding of the file. See menu encoding, switch to utfß. – Mensch Oct 31 '14 at 9:54

\documentclass[]{book}