Re: Getting UTF-16 encoding on dynamic content regardless of output content type

2022-03-31 Thread Christopher Schultz
Greg, On 3/31/22 12:17, Christopher Schultz wrote: Greg, On 3/29/22 13:41, gelo1234 wrote: Have you also tried HTMLT or XHTMLT Serializers? Default HTMLSerializer cannot handle some unicode characters: https://issues.apache.org/jira/browse/SLING-5973?attachmentOrder=asc Hmm. Are the HTMLT

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

2022-03-31 Thread Cédric Damioli
Hi, To help isolate the issue, could you test with a simpler pipeline with only generator/single simple XSLT/xml serializer ? Cédric Le 31/03/2022 à 17:54, Christopher Schultz a écrit : Cédric, On 3/29/22 12:52, Cédric Damioli wrote: Do you use Xalan as XSLT Processor ? If so, I remember

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

2022-03-31 Thread Christopher Schultz
Greg, On 3/31/22 12:13, Christopher Schultz wrote: On 3/29/22 13:37, gelo1234 wrote: Hello Chris, I think you will not get any icon-type character on output without using proper font rendering - like Emoji support? Emoji might not be supported by default in Cocoon. This isn't a

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

2022-03-31 Thread Christopher Schultz
Greg, On 3/29/22 13:41, gelo1234 wrote: Have you also tried HTMLT or XHTMLT Serializers? Default HTMLSerializer cannot handle some unicode characters: https://issues.apache.org/jira/browse/SLING-5973?attachmentOrder=asc Hmm. Are the HTMLT / XHTMLT serializers built-in? I have disabled all

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

2022-03-31 Thread Christopher Schultz
Greg, On 3/29/22 13:37, gelo1234 wrote: Hello Chris, I think you will not get any icon-type character on output without using proper font rendering - like Emoji support? Emoji might not be supported by default in Cocoon. This isn't a font-rendering issue; it's just ... wrong. Either the

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

2022-03-31 Thread Christopher Schultz
Cédric, On 3/29/22 12:52, Cédric Damioli wrote: Do you use Xalan as XSLT Processor ? If so, I remember https://issues.apache.org/jira/browse/XALANJ-2617 which could be a cause of your issue. I resolved it on my side years ago by compiling my own patched version > of Xalan. I'm using