Mark wrote:
Thanks for the swift responses.
Alice, to clarify, my output currently gives me:
<a href="#!-- #ID=doba_io89456.sl2098796 --#"> in my html anchors. The
doba part is the name of the original xml file listing that is passed
to the processor using the document function.
My intention is to output:
<a href="#!-- #ID=param-test_io89456.sl2098796 --#"> where param-test
is the name of the processed file that is listed in doba.xml.
I'll explore the tunnel parameters further. This was a suspected
option but I was having trouble finding correct syntax so hopefully
Eliot's sample code will put me on the right road.
Another tip: a very easy-to-make and hard-to-diagnose mistake is
forgetting to specify tunnel="yes" on the param statements in templates
that need the parameter, especially if you're refactoring from
untunneled to tunneled parameters.
It just occurs to me now that one could use a simple XQuery to generate
a parameter use report for an XSLT that would help diagnose that
problem. Will post when I have it worked out.
Cheers,
Eliot
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 610.631.6770
www.reallysi.com
www.rsuitecms.com
--~------------------------------------------------------------------
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>
--~--