Hi Chris,
I suppose you cannot use 2 different encodings in 1 Serializer, so if you
changed
your Serializer config to be UTF16, you also have to use _external_ UTF16
encoded
CSS styles. Of couse you can define many different Serializer configs per
each pipeline.
By default common-lang/cocoon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 6/20/17 4:11 PM, Christopher Schultz wrote:
> Greg,
>
> On 6/8/17 2:17 PM, gelo1234 wrote:
>> Chris,
>
>> Even with C3 (cocoon 3.0 beta) unless you specify optional
>> encoding in your Serializer config, you fallback to default
>> UTF-8:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Greg,
On 6/8/17 2:17 PM, gelo1234 wrote:
> Chris,
>
> Even with C3 (cocoon 3.0 beta) unless you specify optional encoding
> in your Serializer config, you fallback to default UTF-8:
>
>
Chris,
Even with C3 (cocoon 3.0 beta) unless you specify optional encoding in your
Serializer config, you fallback to default UTF-8:
org.apache.cocoon.optional.servlet.components.sax.serializers.util
public class ConfigurationUtils {
private ConfigurationUtils() {
}
public static
It depends on what type of Serializer you use and what kind of Serlializer
config you put into your sitemap?
By default XMLSerializer/HTMLSerializer uses UTF-8 encoding. So instead of
1 UTF-16 char you got 2 chars UTF-8 encoded.
Of cource there might be also issue with emoji charset, but I would
I had a related problem with 3–4 CJK characters being converted to their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
I've been testing my application for use with high Unicode code points
such as emoji like which is this one:
http://www.fileformat.info/info/unicode/char/1F60D/index.htm
My application and database can handle this code point, but Cocoon
