AW: [xsl] use preceding element or self

["Klocker Christoph" <Christoph.Klocker@xxxxxxxxxxxxx>]

The expression:

(preceding::par[@class='Komm_H3'])[text()[1][normalize-space()]][not(con
tains(text()[1],','))[1]][last()]

gave me different results while transforming with saxon8.2 and evaluating with
xmlspy xpath2.0 evaluator. Meanwhile I changed to saxon8.4 and they deliver
the same result.

When transforming my sample file (see last email), it still gives me two
different results, (same with xmlspy xpath evaluator), once the expression
selects the string (UMSATZSTEUER) and the other time whole node. On my real
xmls strangely it always selects the whole node, instead of the required
string.

Couldn't figure it out why??

Christoph




-----Urspr|ngliche Nachricht-----
Von: Michael Kay [mailto:mike@xxxxxxxxxxxx]
Gesendet: Freitag, 29. April 2005 13:20
An: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Betreff: RE: [xsl] use preceding element or self

> > Seems to be a Saxon issue.

I haven't been following this thread as DC seemed to have it under control.
If you think you've got a Saxon issue, please could you explain it from
first principles so I don't have to follow the thread back. Thanks.

Michael Kay
http://www.saxonica.com/