Re: Entity escaping in o.a.c.c.serializers.XHTMLSerializer

2009-01-22 Thread Andreas Hartmann
Andreas Hartmann schrieb: Andreas Hartmann schrieb: The XHTMLSerializer, or, more specifically, the XHMLEncoder, from the serializers block in Cocoon 2.1.x escapes all characters with a corresponding HTML 4.0 character entity reference into this entity reference. This causes issues with

Re: Entity escaping in o.a.c.c.serializers.XHTMLSerializer

2009-01-22 Thread Antonio Gallardo
Hi Andreas, We hit the same issue some years ago and we found a more pragmatic solution: In org.apache.cocoon.components.serializers.encoding.XHTMLEncoder add the line marked with a + sign: private static final char ENCODINGS[][][] = { +{ { 39 } , #39;.toCharArray() }, { { 160 }

Re: Entity escaping in o.a.c.c.serializers.XHTMLSerializer

2009-01-22 Thread Andreas Hartmann
Hi Antonio, thanks for your reply! Antonio Gallardo schrieb: We hit the same issue some years ago and we found a more pragmatic solution: In org.apache.cocoon.components.serializers.encoding.XHTMLEncoder add the line marked with a + sign: private static final char ENCODINGS[][][] = { +

Re: Entity escaping in o.a.c.c.serializers.XHTMLSerializer

2009-01-22 Thread Antonio Gallardo
Andreas Hartmann escribió: Unfortunately it doesn't work for me. The XHTML source contains the NCR for the ' character which also causes a JavaScript error. To make it work, it would have to look like this: private static final char ENCODINGS[][][] = { { { 34 } , \.toCharArray()

Entity escaping in o.a.c.c.serializers.XHTMLSerializer

2009-01-21 Thread Andreas Hartmann
Hi Cocoon devs, this issue has already been discussed several times, e.g. [1], but AFAIK has not been resolved yet. The XHTMLSerializer, or, more specifically, the XHMLEncoder, from the serializers block in Cocoon 2.1.x escapes all characters with a corresponding HTML 4.0 character entity

Re: Entity escaping in o.a.c.c.serializers.XHTMLSerializer

2009-01-21 Thread Andreas Hartmann
Andreas Hartmann schrieb: The XHTMLSerializer, or, more specifically, the XHMLEncoder, from the serializers block in Cocoon 2.1.x escapes all characters with a corresponding HTML 4.0 character entity reference into this entity reference. This causes issues with inline JavaScript, since e.g.