RE: [xsl] AltovaXML bugs? (and other engines)

Subject: RE: [xsl] AltovaXML bugs? (and other engines)
From: Scott Trenda <Scott.Trenda@xxxxxxxx>
Date: Tue, 31 Mar 2009 20:37:43 -0500
Just a thought (maybe someone's done it already)... is there some sort of Acid
test for XSLT processors? I think there are conformance test packages
available from W3C, but it's usually the experienced XSLT developers who know
how best to break an XSLT engine. It'd be nice to have such a test for both
XSLT 1.0 and XSLT 2.0, since we could know exactly how and where the different
XSLT engines fail.

I'm guessing Michael Kay would know the best place to start here. :)

~ Scott

-----Original Message-----
From: Philip Vallone [mailto:philip.vallone@xxxxxxxxxxx]
Sent: Tuesday, March 31, 2009 8:25 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: [xsl] AltovaXML bugs? (and other engines)


I will report this to Altova tomorrow via their ticket system. They
are continually updating xmlspy, but I have not seen a running list. I
would be interested in seeing dif list also. xmlspy is a great editor
and has a decent xslt processor. Saxon, by far is the best. It's fast
and reliable. Saxonica (Michael Kay) is very good at providing the
very best xslt 2.0 processor.


On Mar 31, 2009, at 9:15 PM, Scott Trenda wrote:

> In response to this... we're using AltovaXML at my work, since its
> license is very business-friendly and it doesn't require a managed-
> code base (Java or .NET) to run. However, I've noticed that when
> compared to Saxon, it gives different output in some places, and for
> the few times I've looked into it, the error is within AltovaXML.
> (Not to mention it's slow compared to Saxon.)
> Is there a list somewhere of known issues within AltovaXML's XSLT
> 2.0 engine? Although we're not using it very often at my work, it'd
> be nice to know what pitfalls to avoid.
> And while I'm asking, does anyone know of a similar list for
> Transformiix (Firefox's XSLT engine) and Opera's XSLT engine? I know
> I've asked for a standalone of Opera's engine before, but this time
> I'd just like to know what these two don't support. I know
> Transformiix doesn't recognize the namespace:: axis, but that's
> about it.
> ~ Scott
> -----Original Message-----
> From: Philip Vallone [mailto:philip.vallone@xxxxxxxxxxx]
> Sent: Tuesday, March 31, 2009 7:03 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [xsl] Counting with xsl:key
> Thanks... works perfect. Actually xmlSPY throws an error if the select
> statement is in the <xsl:number>
> <xsl:number level="any" count="figure[not(@inline='true')]"
> select="key('fig-key', @href)" />
> Saxon runs it as expected... Saxon rocks
> Thanks again,
> Phil

Current Thread