I think it is clear now. It took some time for me (and a clear written
solution).
I think now that Andrew's solution is doing the same - I will have to look
at it again.
The solution is not near what I hoped as it seems to be very slow.
Perhaps I can save the xml making an id-transfer on the whole xml giving
each Y-node an attribute with the maximum number lv of descendants (using
one of the two solutions), then use this attribute in future
transformations. The usefullness of this solution depends on how often the
input xml will change...
Thanks to both of you, and sorry for being so slow.
Ragulf Pickaxe :-)
_________________________________________________________________
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--