Hi Wendell,
Thanks for the reply! Your code worked very well, and solved the problem in my
various tests yesterday and today. Fortunately, this is a temporary solution
while we migrate the customer to an actual element container instead of a
mis-paired tag. Their business rules, which they follow, require them to pair
the tech:revst and tech:revend correctly, and they are always siblings. Our
parser explodes, otherwise.
I'm grateful for the assistance and things I've learned in this code!
Best,
Michael
----------------------------------------
Date: Fri, 30 Jan 2015 19:51:53 +0000
Subject: Re: [xsl] Creating a container element for siblings which have
different start and end elements
From: xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
So here is an approach that might work for you. Note that it assumes
that: (a) your starts and ends are properly paired, and (b) they are
always siblings. It uses a pair of keys to point back and forth
between tech:revst elements and their "contents", i.e. the sibling
nodes to which they apply. Since internally generated identifiers make
a convenient way to key to individual nodes, we use them.
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--