Re: [xsl] xsltproc/LibXSLT - non-compliance?

[David Carlisle <davidc@xxxxxxxxx>]

> difference between xslt 1 processors in browsers and should be
> documented(?).

it's probably easier (should Daniel be watching) to fix the code to work
like the others than it is to document that it is different. But that is
not the same as saying that the existing behaviour is non conformant.
In any case that's really a subject for a libxslt list rather than
xsl-list.

As a comparison, in xslt2 then it's clear that an argument of . is
allowed in function-available and will evaluate to the string value of
the node, but actually this is almost no use at all in an XSLT2 context
as in xslt2 a processor can (and will) generate static errors on a call
to an undefined function even if it is guarded by an xsl:if test on
function-available. In order to avoid static errors you need to use teh
function-available test in a use-when attribute, but they are evaluated
statically before the source document is read, so . is not available at
all.


David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________