Re: disable-output-escaping

Thanks you Martin, altough I still have to disagree. I've read the full 
spec, some times.

Achieving _compliance_ is good, but achieving the OBJECTIVE is what REALLY 
matters.

This issue looks like the kind of decision that is purely based on techincal 
aspects. But even then
I don't see why is so difficult to produce an output document and re-input 
it to the browser.

Anyway, I won't insist anymore. You guys have been doing a great job so far 
and I trust that
in the future you will address this issue

My very best regards and sincere apologies,
Gabriel Blum


"Martin Honnen" <[email protected]> wrote in message 
news:[email protected]...
>
>
> Gabriel Blum wrote:
>
>> I think ... and it's just a humble thought
>>
>> that by definition.... ( taken from http://www.w3.org/TR/xslt )
>> "This specification defines the syntax and semantics of XSLT, which is a 
>> language for transforming XML documents into other XML documents."
>>
>> You know, transforming "documents" into "documents"... That means the 
>> output of the transformation should be a document,
>> not a dom-tree, not anything else;
>
> Well if you want to cite a spec to make your case then read it completely, 
> for instance
>   <http://www.w3.org/TR/xslt#output>
> says: "An XSLT processor may output the result tree as a sequence of 
> bytes, although it is not required to be able to do so (see [17 
> Conformance])"
> and
>   <http://www.w3.org/TR/xslt#disable-output-escaping>
> clearly says: "An XSLT processor is not required to support disabling 
> output escaping."
>
> -- 
>
> Martin Honnen
> http://JavaScript.FAQTs.com/