Re: Frustrated with xxx:node-set

Thanks Dimitre.  I will be approaching this with MSMXL3,  as
aggregation/summary of this nature is HUGEly necessary to accomplish
those things I need to.
Later, I will adopt the parser available to .NET.

Karl..

On 6/1/05, Dimitre Novatchev <dnovatchev@xxxxxxxxx> wrote:
> Sorry Karl,
>
> I have misled you --  transforming with exMsxsl still produces the
> wrong result  --- I took
>
> <foobar_summary>  (which comes with content)
>
> for
>
> <summary_for_foo>
>
>
> So, you have to either modify your code to avoid this bug or start
> using MSXML3 or another XSLT processor.
>
>
> Cheers,
> Dimitre Novatchev
>
>
>
>
> On 6/2/05, Karl Stubsjoen <kstubs@xxxxxxxxx> wrote:
> > Not trying to access the stylesheeet as you suggested, using exmsxl
> > command line interface to do so.
> >
> > I have had success using msxsl and specifying ver. 3.0 which returns
> > the output I am expecting, the problem there is that 3.0 does not
> > offer support for the ms function format-date; no biggy, I don't mind
> > losing that feature.
> >
> > Thanks..
> >
> > Dimitre, any more ideas on the exMsxsl dilemna I am having?
> >
> > On 6/1/05, Bovy, Stephen J <STEPHEN.Bovy@xxxxxx> wrote:
> > > 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)