Hi,

> Your snippet says: "any time you see a record, copy it to 
> output including
> descendents. Add an element stop and set its value to the value of the
> preceding record/start element.". Right?

Yes, the first record in reverse document order.
 
> But it won't do that.

What do you get, then? Which processor do you use? You don't get the results you specified in you original email with the source provided and with those two templates only?
 
> And I do not know where to start and how to debug this.
> 
> However, the missing point in my thought was "preceding::record[1]" or
> "../preceding-sibling::record[1]" in order to reference the preceding
> record.

Oh yes, you should use 
 
  preceding-sibling::record[1]/start

but in your case it shouldn't matter which you use. You don't want to use the parent axis (..) in the expression, because then you'd end up in the base element.

Cheers,

Jarno - Dulce Liquido: Antichristiano

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list