I think we have to agree that we disagree. I don't consider the presence of a divergence in other implementations to be sufficient evidence by itself that we should copy that divergence.
But that's just my own opinion; we'll see what the rest of the developers think.
___
On Wednesday 10 July 2002 06:25, Joseph Kesselman wrote:
> Which is why it's being corrected in XSLT 2.0.
Yes, that is a Good Thing. Unfortunately, we're stuck with 1.0 for another
year or so. (BTW, has Xalan made any moves towards supporting 2.0? Will
that be Xalan3 or something?)
> But a
On Tuesday, 07/09/2002 at 03:11 MST, Peter Davis <[EMAIL PROTECTED]> wrote:
> On Tuesday 09 July 2002 14:28, Joseph Kesselman wrote:
> > The point of standards is that they _ARE_ standards, and you should be very
> > explicit about when you're stepping outside their scope.
>
> The problem is that
On Tuesday 09 July 2002 14:28, Joseph Kesselman wrote:
> The point of standards is that they _ARE_ standards, and you should be very
> explicit about when you're stepping outside their scope.
The problem is that the standard in question was very short sited, placing
this unecessary restriction o
> > XSLT 2.0 allows Temporary Trees (new name for RTFs) to be treated directly
> > as nodesets, but we can't do that in a fully compliant 1.0 implementation.
>
> Would it be possible to enable by some configuration option a "quirks mode"
> where it is possible to use an RTF as a node-set?
Speaki
On Tuesday 09 July 2002 06:01, Joseph Kesselman wrote:
> XSLT 2.0 allows Temporary Trees (new name for RTFs) to be treated directly
> as nodesets, but we can't do that in a fully compliant 1.0 implementation.
Would it be possible to enable by some configuration option a "quirks mode"
where it is
>Using the latest xalan (don't know about the behaviour in previous
>versions) I cannot wrap an xsl:for-each as a variable e.g.
>name="test"> I
>get a 'cannot convert tree fragment to node-list exception'.
>However, if I put the 'for each' in a template I can wrap the return from
>this templat
t
Boag/Cambridge/IBM)
Subject: xsl-for-each
07/09/2002 02:47
Just a general posting as I am not sure if it is a bug or a feature of xsl.
Using the latest xalan (don't know about the behaviour in previous
versions) I cannot wrap an xsl:for-each as a variable e.g. I
get a 'cannot convert tree fragment to node-list exception'.
However, if I put the 'for ea
