You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Benedikt Ritter (JIRA)" <ji...@apache.org> on 2014/07/10 20:32:06 UTC
[jira] [Updated] (CSV-35) Escaped line separators are not supported
[ https://issues.apache.org/jira/browse/CSV-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedikt Ritter updated CSV-35:
-------------------------------
Fix Version/s: (was: 1.0)
1.x
As discussed on the ML, I'm moving this to 1.x, so we can release 1.0. [1]
I've implemented logic that makes sure only record separators, we can handle are used.
[1] http://markmail.org/message/2ba52lsduzc5jisr
> Escaped line separators are not supported
> -----------------------------------------
>
> Key: CSV-35
> URL: https://issues.apache.org/jira/browse/CSV-35
> Project: Commons CSV
> Issue Type: Bug
> Reporter: Emmanuel Bourg
> Fix For: 1.x
>
> Attachments: CSV-35.patch, commons-csv CSV-35 escapeCRLFOnce test.patch, commons-csv CSV-35 escapeCRLFOnce.patch, mysql-export-line-terminated-by-crlf.csv, mysql-export-line-terminated-by-lf.csv
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)