Elegant support for DOS or posix newlines

[ebolyen (Evan Bolyen)]

Turns out it was a byte-order mark:

FASTQ Files Importing Error

Just to provide some closure, I think I found the issue: (via hexdump -C <filename>) 00000000 ef bb bf 73 61 6d 70 6c 65 2d 69 64 2c 61 62 73 |...sample-id,abs| 00000010 6f 6c 75 74 65 2d 66 69 6c 65 70 61 74 68 2c 64 |olute-filepath,d| 00000020 69 72 65 63 74 69 6f 6e 0d 0a 35 30 30 36 34 2c |irection..50064,| First column is position, next two are the bytes as a single hex number and finally the ASCII value (if it is a visible character, otherwise it will be a dot) Here we see tha…

We definitely need to fix that! It comes up surprisingly often, although this is the first case of a UTF-8 BOM. Most of the BOMs are only 2 bytes and from UTF-16.