This information comes from someone much more knowledgable about XML/XSL
transforms then I. And it works.
There is "a small quirk in the wonderful world of XSL transforms. In a
nutshell although XSL transformations can produce adhoc output - there are
many areas where the XSL breaks down if it isn't producing XML. This being
one of those areas.
So all they need to do is produce XML instead of text and then dig out the
After creating and loading the myDoc and myStyle DOMs use the following code
to transform and output the text:
' Transform using XSL
myDoc.transformNodeToObject myStyle, myRet
Print #1, myRet.documentElement.Text
> The parser has knowledge of the CDATA parameter when the DOM is being
> loaded. Therefore the & is correct in the DOM. However, when the
> TransformNode() is performed the knowledge of CDATA has not been carried
> forward. The DOM then replaces "&" with "&" for its own use. It is
> then returned from the TransformNode() with the & still in place.
> If anyone can solve this issue it would be greatly appreciated.
> David Fowler
> Bottomline Technologies (de), Inc.
> > Can anyone tell me why this isn't working in my stylesheet?
> > <TD><![CDATA[ ]]></TD>
> > I tranform the node on the server, but doubt that has anything to do
> > because I have used before in Response.Write() with ASP. Is there
> > possibly another way I can put amerpsands in my stylesheet?
> > BTW, just using
> > <TD> </TD>
> > outputs HTML as
> > <TD>&nbsp;</TD>
> > TIA
> > Heath Stewart