You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Minto van der Sluis (JIRA)" <ji...@apache.org> on 2014/07/28 12:06:38 UTC
[jira] [Commented] (CLEREZZA-929) Add support for other text
encodings beside UTF-8 for Resultset message body writers
[ https://issues.apache.org/jira/browse/CLEREZZA-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076057#comment-14076057 ]
Minto van der Sluis commented on CLEREZZA-929:
----------------------------------------------
This has only been applied to Tsv and Csv writers since it seemed most applicable. Json has been skipped since UTF-8 is Json's default text enconding. Xml has also been skipped since the implemention does not directly deal with text enconding.
> Add support for other text encodings beside UTF-8 for Resultset message body writers
> ------------------------------------------------------------------------------------
>
> Key: CLEREZZA-929
> URL: https://issues.apache.org/jira/browse/CLEREZZA-929
> Project: Clerezza
> Issue Type: Bug
> Reporter: Minto van der Sluis
> Assignee: Minto van der Sluis
>
> Component: jarxrs.rdf.providers
> Version: 0.15
> The CSV and TSV Message body writers only support UTF-8. The resulting CSV cannot easily be read by Microsoft Excel. For details see: http://stackoverflow.com/a/155176
> To work around this it would be really nice to be able to use the standard windows text encoding Cp1252 for the generated CVS file.
--
This message was sent by Atlassian JIRA
(v6.2#6252)