[
https://issues.apache.org/jira/browse/JENA-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660719#comment-13660719
]
Andy Seaborne commented on JENA-459:
------------------------------------
I get the same and no, it's not fine.
Either write ASCII or write UTF-8.
In fact, I'm thinking of making it two writers for NT (and 2 for NQ). One that
is ASCII only (IRIs and literals) for use with text/plain and one that is
UTF-8, for use with application/n-triples, or even text/plain;charset=utf-8.
Pure UTF-8 would be the preferred form - the default for the language N-TRIPLES.
> Literals in ntriples not unicode escaped
> ----------------------------------------
>
> Key: JENA-459
> URL: https://issues.apache.org/jira/browse/JENA-459
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ, Jena, RDF API
> Affects Versions: Jena 2.10.1
> Environment: everywhere
> Reporter: Pascal Christoph
> Assignee: Andy Seaborne
> Priority: Minor
>
> Unicode escaped characters like "\u005A" are string of 1 character and should
> be rendered as such when file encoding is UTF8 . Serializing ntriples, this
> is working for such escaped characters residing in URIs, but when used in
> literals the escaping is ignored. Thus, in literals "\u005A" is written as a
> string of 6 characters rather than a string of one, while in URIs there is 1
> character.
> Using e. G. 'RDFDataMgr.write(System.out, model, Lang.TURTLE) the same model
> results as expected, though. The problem just arises when using NTriples .
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
