commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (CSV-35) Escaped line separators are not supported
Date Mon, 24 Jun 2013 14:22:20 GMT


Sebb commented on CSV-35:

Yes - see my comment dated 29/Mar/12 16:13.

i.e. the escape char only affects the subsequent character.

I suppose <esc>CRLF could be special-cased if it is likely to be needed.

However how does one then support the current behaviour - again, if there is a user-case for
There could be switchable option, but that would only work for the complete file.
> Escaped line separators are not supported
> -----------------------------------------
>                 Key: CSV-35
>                 URL:
>             Project: Commons CSV
>          Issue Type: Bug
>            Reporter: Emmanuel Bourg
>             Fix For: 1.0
> Commons CSV doesn't handle escaped line separators, for example:
> {code}
> value1;value2;value3a\
> value3b
> {code}
> In this case the expected result is:
> {code}["value1", "value2", "value3a\nvalue3b"]{code}
> This kind of escaping is produced by MySQL, whether the field enclosing is enabled or
not. It's possible to see enclosing quotes and escaped line separators like this:
> {code}
> "value1";"value2";"value3a\
> value3b"
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message