Re: transform mixing up namespaces

One way to use MSXML3 from the console prompt is to download

http://msdn.microsoft.com/msdn-files/027/001/485/XSLTCommandLine.exe


Your example transforms correctly with Xalan C++ 1.1 (which is closer in
code to Xalan 2.0 for Java)

Maybe you should go to 2.0 if you want to stay with Xalan

-------------------------------------------------
Michael Beddow
http://www.mbeddow.net/


----- Original Message -----
From: "Huebel, David" <dhuebel@xxxxxxxxxxxxxx>
To: <XSL-List@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Thursday, May 24, 2001 2:19 PM
Subject:  transform mixing up namespaces


> Hello all,
>
> My xsl transform seems to be mixing up namespaces.  In the simplified
> example below, the "content" element is in the null namespace in the
> transform, but in the result, it appears to be in the default
namespace,
> which is bound to "uri:foo".  Is this correct behavior, and if so,
why, and
> how can I get the transform to leave the content element in the null
> namespace?
>
> I am using Xalan 1.2.  (Another behavior that is annoying, but correct
as
> far as I know, is that Xalan will create result documents with unused
> namespace declarations.  See an example at the bottom of this email.)
>
> Another question:  I use IE5 and the latest version of MSXML to view
xml
> documents with the <?xml-stylesheet?> directive.  Can I use MSXML to
> transform documents from the command line (without buying anything)?
>
> Thanks,
>
> David
>



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