#44 Enable to use hard line-ending

[FractalizeR]

I have a CSV file, that uses \r\n as a line-ending, but it also have some unescaped and unquoted \n characters as a part of a field. This leads most CSV parsers to fail.

Can we have a feature to use line-endings not only when saving a CSV file, but also when reading? Currently the documentation says: "this preference won't be used at all for reading".

I suppose any \n or \r\n in this case will be treated as an end-of-line character.

[Hannu Klemetti]

We have this same problem and what I found out is that this actually seems to be a bug in SuperCSV. CSV specification (RFC 4180) defines line break as CRLF (\r\n). It would be nice if it were supported to define exclusively the line break, because there is always someone who implements against specification.

[James Bassett]

Migrated to GitHub issues: https://github.com/super-csv/super-csv/issues/5