[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: dealing with CDATA (was dealing with CDATA on the client-side)


Subject: RE: dealing with CDATA (was dealing with CDATA on the client-side)
From: eric@xxxxxxxxx (Eric Costello)
Date: Wed, 7 Jun 2000 17:35:29 -0500

Thanks to all for your responses! I am not having a lot of luck, though. I
downloaded and installed the may MSXML release, gave her a reboot, and tried
out some of the suggested solutions. Here is a major problem I am having:

>From Paulo's example:
> XSL File:
>
> <?xml version="1.0" encoding="ISO-8859-1" ?>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >

When I try to use the http://www.w3.org/1999/XSL/Transform namespace, the
transform returns the content of my XSL file instead of transformed XML.

The following link (http://msdn.microsoft.com/xml/xslguide/xsl-debug.asp)
has this to say on that matter:
<SNIP>
Problem:
	Elements with the XSL Namespace Appear in Output
Solution:
	Elements from the XSL namespace appearing in the output indicate that the
XSL namespace declaration is using an incorrect URL. The XSL processor
doesn't recognize these elements as XSL elements and treats them as output
elements. The correct namespace identifier for XSL is
http://www.w3.org/TR/WD-xsl.
</SNIP>

But there are examples in other Microsoft documentation
(http://msdn.microsoft.com/xml/general/msxmlprev03152000.asp, scroll to the
first example) that use the http://www.w3.org/1999/XSL/Transform namespace.
What is going on, and why can't I get it to work?

Thanks,
Eric


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



Current Thread
Keywords
xsl