You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current Yanel / Yarep only supports UTF-8 encoded XMLs (<?xml version="1.0" encoding="UTF-8"?>).
So while you technical "can" save emojis in such an XML, the Xerces Parser (2.11) will fail, because Emoticons are not allowed in UTF-8 XMLs.
So is there any solution how to use UTF-16 XMLs with Yanel?
A workaround would be to violate the rules and store Emojis in the current UTF-8 XMLs and avoid using Xerces (which means in the Yanel-Apps: never use the BasicXMLResource.java:getTransformedInputStream() method). Instead, the resource could read the XML via JAXB into a Java Bean and then pass the content from that to XSLT, like:
But I don't like the approach that you have to hardcode every property that you want to pass up to XSL. It should be something that also passes up ALL the elements in the XML, so also a 1:1 approach like the Xerces one...
Any ideas?
The text was updated successfully, but these errors were encountered:
Another workaround: you simply remove all Emojis in your application by filtering all input texts that can be submitted by users. For this I can recommend this library: https://github.com/vdurmont/emoji-java , you just use EmojiParser.removeAllEmojis(string). In my case this works great.
The current Yanel / Yarep only supports UTF-8 encoded XMLs (
<?xml version="1.0" encoding="UTF-8"?>
).So while you technical "can" save emojis in such an XML, the Xerces Parser (2.11) will fail, because Emoticons are not allowed in UTF-8 XMLs.
So is there any solution how to use UTF-16 XMLs with Yanel?
A workaround would be to violate the rules and store Emojis in the current UTF-8 XMLs and avoid using Xerces (which means in the Yanel-Apps: never use the BasicXMLResource.java:getTransformedInputStream() method). Instead, the resource could read the XML via JAXB into a Java Bean and then pass the content from that to XSLT, like:
But I don't like the approach that you have to hardcode every property that you want to pass up to XSL. It should be something that also passes up ALL the elements in the XML, so also a 1:1 approach like the Xerces one...
Any ideas?
The text was updated successfully, but these errors were encountered: