[
https://issues.apache.org/jira/browse/CSV-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13851046#comment-13851046
]
Emmanuel Bourg commented on CSV-102:
------------------------------------
Ok understood. I'm under the impression it would add a fair amount of
complexity for a case that might never be used. commons-csv doesn't aim at
parsing any structured text format that vaguely look like a CSV file. Having
records separated by a line break looks like a minimal expectation to me.
If it's really necessary to parse a file with a record separator other than a
line break I would suggest preprocessing the file to transform the separators
into line breaks before feeding it to commons-csv. But that task would be out
of the scope of commons-csv.
> Commons CSV does not properly handle record separators
> ------------------------------------------------------
>
> Key: CSV-102
> URL: https://issues.apache.org/jira/browse/CSV-102
> Project: Commons CSV
> Issue Type: Bug
> Affects Versions: 1.x
> Environment: ALL
> Reporter: Oliver Oyston
> Priority: Minor
> Attachments: Changes.patch, nonstandard.patch
>
>
> Any specified record separator appear to be ignored and the code just assumes
> that standard line endings are the record delimiters.
> I have a patch to partly address the problems that 'falls back' to the
> current behavior. The patch only allow a maximum of a one character record
> separator.
> The approach needs verifying and also needs improving to be more generic.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
