Return-Path: X-Original-To: apmail-commons-issues-archive@minotaur.apache.org Delivered-To: apmail-commons-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 69F8511DEB for ; Wed, 18 Jun 2014 11:13:04 +0000 (UTC) Received: (qmail 68151 invoked by uid 500); 18 Jun 2014 11:13:04 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 68044 invoked by uid 500); 18 Jun 2014 11:13:04 -0000 Mailing-List: contact issues-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: issues@commons.apache.org Delivered-To: mailing list issues@commons.apache.org Received: (qmail 68031 invoked by uid 99); 18 Jun 2014 11:13:03 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Jun 2014 11:13:03 +0000 Date: Wed, 18 Jun 2014 11:13:03 +0000 (UTC) From: "Thomas Neidhart (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CSV-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035579#comment-14035579 ] Thomas Neidhart commented on CSV-35: ------------------------------------ This issue is related to CSV-102. The patch there adds support for custom record separators when parsing, similar to my patch. Although I think that the ExtendedBufferedReader should not be changed, as CR/LF is used there to get the actual line number of the parsed file for error handling / debug information only. > 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 > > Attachments: CSV-35.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)