[
https://issues.apache.org/jira/browse/JENA-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13890764#comment-13890764
]
Andy Seaborne commented on JENA-636:
------------------------------------
It may not (just) be the plugin. schemagen.java has:
{noformat}
m_output = new PrintStream( new FileOutputStream( out ) );
{noformat}
which looks suspicious. It opens the PrintStream with the platform default
character encoding.
See also : FileUtils.asPrintWriterUTF8.
> No configuration option for setting output encoding in schemagen
> ----------------------------------------------------------------
>
> Key: JENA-636
> URL: https://issues.apache.org/jira/browse/JENA-636
> Project: Apache Jena
> Issue Type: Bug
> Components: Cmd line tools
> Affects Versions: Jena 2.11.1
> Reporter: Ian Dickinson
> Assignee: Ian Dickinson
> Priority: Minor
>
> User reported a problem that Java source files generated by schemagen are
> only created with character encoding cp1252, whereas his source files need to
> be in UTF-8 to cope with international characters in the ontology content.
> At present, there is no configuration option to set the character encoding on
> the output file, so this would need to be added to schemagen.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
