Ah yes, then the processor can do some optimization and stop looking for
'anchor' processing instructions right after the first anchor PI has
been found on the preceding axis.
On 10.04.2017 16:35, Erik Zander
erik(_dot_)zander(_at_)studentlitteratur(_dot_)se wrote:
Thanks Gerrit,
You pointed me in the right direction so I could avoid the timeout :)
The solution was close at hand
<xsl:variable name="currentPage"
select="substring-before(substring-after(./preceding::processing-instruction('anchor')[1], 'Page.'),
'"')"/>
Just using the fact that preceding is in reverse order :)
Regards
Erik
--~----------------------------------------------------------------
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
--~--