RE: Frustrated with xxx:node-set

Are you trying too access the style sheet within your xml doc
with a processing instruction ???

<?xml-stylesheet type="text/xsl"
  href="'test.xsl" ?>

If so you are stuck with MSXML3   ....

Also the most current version of MSXML3 must be installed in replace
mode ..

MSXML4 or msxml5 delivered with office 2003 can only be accessed thru
script code which really [expletive deleted].

I wish microsoft would provide a patch to fix this.

-----Original Message-----
From: Karl Stubsjoen [mailto:kstubs@xxxxxxxxx]
Sent: Wednesday, June 01, 2005 3:33 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Frustrated with xxx:node-set

Uggg... just modified the xslt decleration to:

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
	xmlns:fx="http://exslt.org/common">

..and still miss-behaving : (

Oddly enough, works if I change the 4.0 to 3.0 like this:
exmsxsl foobar.xml get_foobar.xsl -o result.xml -u '3.0*ex'

So wondering if I am still hooked into Microsoft's MSXML Lib somehow.


On 6/1/05, Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrote:
> On 6/2/05, Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
> > Hi Dimitre, thanks for the tips!  Just tested your exMSXSL parser
with:
> > exmsxsl foobar.xml get_foobar.xsl -o result.xml -u '4.0*ex'
> >
> > But seems to have produced the same buggy response as msxm4.  Could
> > I have done something wrong on install?
>
> You have to modify your xslt code: switch from the microsoft namespace
to:
>
>  "http://exslt.org/common"
>
> Cheers,
> Dimitre Novatchev.
>
> > (I dropped the exMsxsl.exe file
> > in my Window 32 directory -- after running the setup.exe file)