Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 21 Jan 2014 02:57:22 +0000 (UTC)
From: "Gary Gregory (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12545640.1331206169369.37635.1390273042472@arcas>
In-Reply-To: <JIRA.12545640.1331206169369@arcas>
References: <JIRA.12545640.1331206169369@arcas>
Subject: [jira] [Commented] (CSV-35) Escaped line separators are not
 supported
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CSV-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877129#comment-13877129 ] 

Gary Gregory commented on CSV-35:
---------------------------------

So, not addressing this means that we cannot deal with MySQL exports? That seems harsh (for users).

It sounds like, for users, the way to tell [csv] about this is with a withMySQLEol(boolean) option? Which would be a special case as Sebb mentioned.

> 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.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 was sent by Atlassian JIRA
(v6.1.5#6160)