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

Jacek Grzebyta edited comment on ANY23-388 at 8/11/18 4:43 PM:
---------------------------------------------------------------

Thanks for example.

If you do not mind I do not think it is good idea to create customised writer. 
UTF-8 is wildly accepted standard. IMHO your code might be put into the 
NTriplesWriter directly (or in NTriplesWriterFactory). -Maybe it is worth to 
add new command line argument to switch on/off the option for the writer.- That 
might be the next step. 


was (Author: grzebyta.dev):
Thanks for example.

If you do not mind I do not think it is good idea to create customised writer. 
UTF-8 is wildly accepted standard. IMHO your code might be put into the 
NTriplesWriter directly (or in NTriplesWriterFactory). Maybe it is worth to add 
new command line argument to switch on/off the option for the writer.

> It should be possible to configure the NTriplesWriter to use unicode points
> ---------------------------------------------------------------------------
>
>                 Key: ANY23-388
>                 URL: https://issues.apache.org/jira/browse/ANY23-388
>             Project: Apache Any23
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.2
>            Reporter: Lars G. Svensson
>            Priority: Minor
>
> When using the NTriplesWriter, I wanted to configure it to write unicode 
> points as escape sequences. I tried to subclass 
> org.apache.any23.writer.TripleHandler and overwrite the access to the 
> org.eclipse.rdf4j.rio.ntriples.NTriplesWriter but couldn't do that since the 
> access to the NTriplesWriter is package protected. I ended up copying the 
> code which seems a bit clunky...
> I was [asked to create a pull 
> request|https://mail-archives.apache.org/mod_mbox/any23-user/201808.mbox/%3CCAGaRif3KAQbnK6XSKnVUZAJOn8aR_iCmJmGv_L05yg6nBkB%3DwA%40mail.gmail.com%3E],
>  this issue is there to track that.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to