I can't remember whether we already mentioned that you can capture a
template's results into a variable, which can also help avoid extensions:
Of course that doesn't return the original nodes, just the result
generated by the template. And in XSLT 1.0, if you
kesh...@us.ibm.com wrote:
The implementation details of calling a template are significantly
different from those of calling an external function. I don't think you're
going to be able to make this work easily.
Suggestion: Can you rewrite the template you want to invoke as an XPath?
If so, yo
The implementation details of calling a template are significantly
different from those of calling an external function. I don't think you're
going to be able to make this work easily.
Suggestion: Can you rewrite the template you want to invoke as an XPath?
If so, you could use that directly in
Hi all,
I am trying to enhance the readability of my XSL code.
One of the options is to reduce things like named template calls to
function calls; for example:
can be reduced to:
which is shorter and more readable.
However this requires the re-implementation of each named tem
