Just saying, great timing. Because I just today had this discussion covering everything on the list. Different character encodings in file, fields which contain

Just saying, great timing. Because I just today had this discussion covering everything on the list. Different character encodings in file, fields which contain line feeds, fields which contain field delimiters without escaping or using quotes and so on. But that's very common. People use whatever source for data, copy paste it into Excel and then think it's good CSV after that. I usually handle CSV as required, every file can be and usually is different. You'll write I/O code according case specific requirements. In many cases, this means some manual fixing and custom parser. -> Job done. Edit: Honestly, I don't even remember when I would have seen RFC4180 compliant file. That's just the truth out there.