> I'm tempted to abandon CSV entirely and just write a routine that will take a line of csv data and burst it directly
good luck with quoting rules and embedded separators.
The real problems seems to be that you don't really get the difference between ISO encodings and UTF8 and that ASCII is a subset of all of them and you keep guessing.
The exporter you used was configured to deliver an UTF8 encoded file with a BOM.
If the actual characters are only in the ASCII range you won't face any other problems. If there where really any characters encoded in "ISO-Latin-1" like ä or è you should be capable to tell right away. (UTF8 will require 2 not 1 byte for them)
FWIW: As a workaround: you should be able to read the whole file into a string, strip the first 3 characters and open a filehandle to that string.
|