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 2075211340 for ; Thu, 10 Jul 2014 19:43:06 +0000 (UTC) Received: (qmail 52932 invoked by uid 500); 10 Jul 2014 19:43:05 -0000 Delivered-To: apmail-commons-issues-archive@commons.apache.org Received: (qmail 52863 invoked by uid 500); 10 Jul 2014 19:43:05 -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 52698 invoked by uid 99); 10 Jul 2014 19:43:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Jul 2014 19:43:05 +0000 Date: Thu, 10 Jul 2014 19:43:05 +0000 (UTC) From: "Benedikt Ritter (JIRA)" To: issues@commons.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CSV-58) Unescape handling needs rethinking 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-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benedikt Ritter updated CSV-58: ------------------------------- Fix Version/s: (was: 1.0) 1.x Moved to 1.x > Unescape handling needs rethinking > ---------------------------------- > > Key: CSV-58 > URL: https://issues.apache.org/jira/browse/CSV-58 > Project: Commons CSV > Issue Type: Bug > Components: Parser > Reporter: Sebb > Fix For: Patch Needed, 1.x > > Attachments: commons-csv.diff > > > The current escape parsing converts to plain if the is not one of the special characters to be escaped. > This can affect unicode escapes if the character is backslash. > One way round this is to specifically check for == 'u', but it seems wrong to only do this for 'u'. > Another solution would be to leave as is unless the is one of the special characters. > There are several possible ways to treat unrecognised escapes: > - treat it as if the escape char had not been present (current behaviour) > - leave the escape char as is > - throw an exception -- This message was sent by Atlassian JIRA (v6.2#6252)