You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2018/03/05 12:25:00 UTC

[jira] [Closed] (SLING-7344) Jackson Sling Model Exporter needs correct character encoding

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

Stefan Seifert closed SLING-7344.
---------------------------------

> Jackson Sling Model Exporter needs correct character encoding
> -------------------------------------------------------------
>
>                 Key: SLING-7344
>                 URL: https://issues.apache.org/jira/browse/SLING-7344
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Chris Millar
>            Assignee: Justin Edelson
>            Priority: Major
>             Fix For: Sling Models Impl 1.4.8
>
>         Attachments: observe-1.png, observe-2.png, observe-3.png
>
>
> This is a formal ticket of what [~justinedelson] and I discussed earlier in December 2017.
> The Jackson Sling Model Exporter needs to correctly set the character encoding so content can be correctly handled. It currently defaults out to ISO-8859-1 which makes displaying localized content impossible.
> I have put together a sample project here: https://github.com/auniverseaway/sling-exporter-sample
> This will show how the default JSON get servlet correctly handles the content, but the Jackson exporter does not. I have also attached screenshots of the behaviors to this ticket.
> It sounded like Justin had ideas on where to solve this, so I will defer to him on where it should be done. If I can help implement a solution in the place you want, let me know. Internally, we cannot use the Jackson Exporter until this is fixed, so it's pretty high priority for me to contribute back if I can.



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