Re: Processing approach

-----Original Message-----
From: Imsieke, Gerrit, le-tex gerrit.imsieke@xxxxxxxxx [mailto:xsl-list-
service@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Monday, July 17, 2017 6:15 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re:  Processing approach

> Ibm not sure whether I have completely understood the scenario, but did
> you consider using tunnel parameters?
>
> https://www.w3.org/TR/xslt-30/#tunnel-params
> https://www.w3.org/TR/xslt20/#tunnel-params
>
> Calculate the variable once, in the context of a node that is
> ancestor-or-self to all affected nodes, and pass this variable as a
> tunnel parameter to apply-templates, to next-match, or to call-template.

Hi Gerrit,
I am stuck with xslt 1 with this task. I suppose the simplest way to describe
it
is the variables created while in one node create foreign key refs against the
obvious matching values I generate while in another path.

Its simpler to use the various logic to generate the values once, then apply
them
at the same time in both locations. Often they are generated while in a for
loop.
However this generates a template call for the large element I am not
currently
processing that ends up copying that node "n" times along with my new appended
element.

In this case, all I really need to do is continually append the secondary
element
to the alternate location as I process and insert a node in the current
position.

Thanks,
jlc