>>This is what disable-output-escaping feature was disagned to facilitate,[color=blue][color=green]
>>see
http://www.w3.org/TR/xslt#disable-output-escaping.
>>disable-output-escaping feature is greately abused by people, but it's
>>primary goal is to allow to output nonXML/nonHTML formats, such as
>>ASP/JSP/XQuery/SQL/etc.[/color]
>
> While Oleg is right about DOE, I'd recommend not to use DOE even in
> such cases (as it may become a little bad habbit).
>
> The attribute value: method="text" was intended for cases exactly like
> this.
>
> Certainly, one has to escape all "<" and "&" characters, but this will
> help to never forget that the result is *not* a well-formed xml
> document.[/color]
I've run into a similar problem, that basically runs along the same
lines. I'm trying to use a FOR XML query with XmlDataDocument and I keep
getting.
<NewDataSet>
<Keywords>
<XML_F52E2B61-18A1-11d1-B105-00805F49916B>
<nodeset>
Nodeset with all special characters escaped.
</nodeset>
</XML_F52E2B61-18A1-11d1-B105-00805F49916B>
</Keywords>
</NewDataSet>
Now, this may simply be a problem with how I'm doing it, but I still
think it might be usefull to have an easy way to convert these to their
character equivlents using XSL.
[color=blue]
> Another approach, which probably is the best compromise between
> convenience and to using 100% conformant features of XSLT, is to use a
> dummy namespace, bind the "asp" prefix to it, perform the
> transformation and then update the result and remove the namespace
> declaration.[/color]
Is there a schema for the asp: tags used with asp.net?