RE: Printing out variables with escaped text.

> Saxon:
> 
> <fake_element_no_escaping>
> <fake_element_escaping>
> 
> Xalan:
> 
> <fake_element_no_escaping>
> <fake_element_escaping>
> 
> which is what I originally wanted.
> 
> It's getting pretty hard to find bugs in Saxon nowadays, so I 
> thought I'd post this to list instead of straight to Mike, to see if 
> anyone had any thoughts on what is the correct behaviour here - the spec 
> doesn't appear to address this issue specifically.

Saxon (by design) supports disable-output-escaping only when writing to the
final result tree, it is ignored when writing to a result tree fragment.

The spec does mention the possibility of d-o-e being retained as a property
of text nodes on a RTF and presumably copied when the RTF is copied, but
like the rest of the spec in this area, it's very much at implementor
option.

There are considerable problems in supporting d-o-e in a stored tree,
especially once you support the node-set() extension, for example you need
to be able to merge adjacent text nodes some of which have d-o-e and others
not.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list