On 26 May 2005, at 11:19, Michael Kay wrote:

disable-output-escaping only works if you are serializing the results of a transformation using a serializer that understands disable-output-escaping. It's not wrong to configure an XSLT processor to produce a result tree without doing such serialization, which is what cocoon appears to do by default, this just means that d-o-e doesn't work in this environment, which is entirely in conformance with the spec.
Generally d-o-e should be avoided for this very reason - it only works if the next stage in the pipeline after the transformation is a d-o-e-aware serializer. This is why the facility is deprecated in XSLT 2.0.

Ah...ok. All is understood now. So it's an issue of cocoon and not of Saxon.