Hi,
On 2/22/2011 9:44 AM, Szabo, Patrick (LNG-VIE) wrote:
I hope I'm imagining this correctly. Couldn't you filter the input
before you do the counting ?!
You could dump the document and sections elements you don't need and
count afterwards.
Yes: Trevor's Gordian knot can be cut by pipelining. Filter the document
first, then run the transformation to generate the output.
A solution in one pass is also possible -- and might even be fairly
clean -- but how it would work best might depend on details of the
filtering requirement. Trevor, you haven't shown us the "filter-output"
template so we don't know what it does and whether it can be refactored
and simplified.
Also, much is possible in XSLT 2.0. For example, if that logic were in a
function instead of a template....
Cheers,
Wendell
--
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
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>
--~--