Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Date: Tue, 31 Jan 2012 21:29:58 +0000 (UTC)
From: "Rob Vesse (Updated) (JIRA)" <jira@apache.org>
To: jena-dev@incubator.apache.org
Message-ID: <2056547813.42.1328045398552.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1685444710.41.1328045398509.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (JENA-207) FmtUtils.stringForNode() does not
 escape tab characters
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JENA-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Vesse updated JENA-207:
---------------------------

    Attachment: FmtUtilsTabEscaping.patch

Fix for FmtUtils.stringEsc() so that it actually escapes tab characters

Also includes an additional test for SPARQL TSV output which was how I spotted this bug originally
                
> FmtUtils.stringForNode() does not escape tab characters
> -------------------------------------------------------
>
>                 Key: JENA-207
>                 URL: https://issues.apache.org/jira/browse/JENA-207
>             Project: Jena
>          Issue Type: Bug
>          Components: ARQ
>    Affects Versions: ARQ 2.9.0
>            Reporter: Rob Vesse
>             Fix For: ARQ 2.9.1
>
>         Attachments: FmtUtilsTabEscaping.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> FmtUtils.stringForNode() delegates literal formatting to FmtUtils.stringForLiteral() which delegates string escaping to stringEsc()
> The issue is that the whitespace escaping section has code to deal with escaping tab characters but has a logical flaw which means tab characters won't hit that code path, the if statement surrounding the white space escapes section checks for the other kinds of whitespace characters but not for tab

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira