I prefer to call, for each `p´, a named template acting
why? (If you are not careful you end up trying to implement the xslt
matching process in xslt which is a big job and unlikely to be
efficient)
What I am having trouble to do is adding a container around a specific
(fixed-order) sequence of those `p´ elements, say, `p[style="a"]´ and
`p[style="b"]´,
The for-each construct posted earlier ought to work just changing the
criterion to style=('a','b')
Does that make sense to you? If so, which way can I go to implement it?
(Tunnel parameters?) Or can you think of other approaches that might be
preferable?
do the grouping on the container element rather than having to pass
information from template to template about whether the element has
already been grouped.
David
--~------------------------------------------------------------------
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>
--~--