> Yes, there's an incompatibility here between XPath 1.0 and 2.0. In 1.0,
> "=" operator compares values as they are. But the < and > operators
> both operands to numbers. This has the strange effect that
> "4" <= "4.0"
> "4" >= "4.0"
> are both true, but
> "4" = "4.0"
> is false.
> In 2.0, there's no implicit conversion: strings are compared as strings,
> using the default collating sequence, and if you want them compared as
> numbers, you have to convert them.
> You can retain the 1.0 behaviour by using backwards-compatibility mode,
> activated when version="1.0" appears in the xsl:stylesheet element (or
All the stylesheets in question have version="1.0" in the xsl:stylesheet
element, but I still got the behavior.
It's not a big deal (I can use Saxon 6 to turn DocBook into PDF), but I
thought I'd mention it.
Bryant Communication Services