[
https://issues.apache.org/jira/browse/SLING-5973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426032#comment-15426032
]
Ben Fortuna commented on SLING-5973:
------------------------------------
In order to create a unit test I'll probably need to do some more investigation
to narrow down where the issue is - I suspect it might be in Cocoon so I'll let
you know if I find anything.
Another interesting aspect of this is that it appears to be outputting the
"surrogate pair" of the unicode character, which is apparently used to
represent UTF-16 characters (which incidentally is the Java internal
representation charset). e.g:
http://apps.timwhitlock.info/unicode/inspect/hex/1F601
Also, lower order unicode characters are output correctly: eg:
{code}☂{code}
> HTMLSerializer not handling some unicode characters (emoji, etc.)
> -----------------------------------------------------------------
>
> Key: SLING-5973
> URL: https://issues.apache.org/jira/browse/SLING-5973
> Project: Sling
> Issue Type: Bug
> Reporter: Ben Fortuna
>
> I've noticed that when I have unicode special characters (e.g. emoji) in my
> sling content and the sling rewriter is enabled the characters are not output
> correctly to the browser. For example:
> {code}😁{code} becomes {code}��{code}
> If I disable the rewriter pipeline the output is as expected.
> I've looked in the code and I suspect the issue is in the HTMLSerializer from
> the Cocoon library, however I'm not sure why as it should be using the
> default encoding for output (which is UTF-8). My rewriter pipeline is using
> the default html-generator and html-serializer provided by sling.
> My code is available on GitHub here:
> https://github.com/Whistlepost/emojistrip
> It provides a very simple app/content project pair with some emoji characters
> in the content (see src/main/resources/SLING-INF/content/phrases.json). Many
> thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
