RE: The XSL-List Digest V2 #562

[Dylan Walsh <Dylan dot Walsh at TSS dot ie>]

>Date: Wed, 22 Mar 2000 16:50:20 GMT
>From: David Carlisle <davidc@nag.co.uk>
>Subject: Re: Disable Output Escaping - really useful
>
>> When the server delivers XML to the browser, 
>
>Yes as I mentioned  disable-output-escaping="yes" is relatively safe
>for transformations done on the server.
>
>but my question is what happens if you have a browser that is rendering
>straight from the output of an _embedded_ xsl engine. Can it be made to
>work then?
>
>Probably this scenario isn't directly relevant to your example of
>pulling something from a database, but it seems to me the main reason
>why people should beware of using this in stylesheets, one day it works,
>and then you try to use the same bit of code in another sheet being used
>in another context and it stops working for a somewhat mysterious
>reason.

If (possibly a big if) browsers fully implement the XSLT 1.0, then they have
to support disable-output-escaping, whatever that may entail for them in
reparsing the output before rendering it. If they do not implement it, then
that is no different than not implementing any other features which are a
part of the XSLT recommendation (e.g. like document() & MSXSL ) in terms of
the potential problems for stylesheet creators.


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