Sam Prokop schrieb am 15.02.2010 um 11:41:21 (+0100):
> I wasn´t aware that compare in Xpath compares to any preceding nodes
> not only the first one.
But of course nothing stops you from going preceding::CCC[1] if that's
what you want - the preceding-axis in in reverse document order, so [1]
wil
Thanks,
this made things clear. I wasn´t aware that compare in Xpath compares to any
preceding nodes not only the first one.
I wanted to archive an Index like:
a | a_c
| a_d
| a_a
b| b_a
| b_d
…
As long as I don´t use substring it worked, if I use substring in the
comparison (substr
Hi, Sam.
Sam Prokop wrote on 02/12/2010 08:53:39 AM:
>
>
>
>
>
>
>
> = select="preceding::CCC"/> :
>
>
> Result:
> A=:false
> A=A:true
> A=A:true
> B=A:false
> B=A:true
> B=A:true
> C=A:false
>
> Does the comparison “CCC = precedin
Hi,
why does Xalan process different current-node-sets, when one node set is sorted?
Example:
XML:
A
B
A
C
B
B
A
XSL: