On Wed, 19 Jan 2011 07:48:11 -0500
"G. Ken Holman" <gkholman(_at_)CraneSoftwrights(_dot_)com> wrote:
The xsl:attribute instructions in an attribute set work just as well
in a called template (though they are executed in real time with the
current node being what it is rather than the current node being the
root).
Perhaps you could despatch to the appropriately named called template
by creating a despatch called template that knows the name of each of
the attribute set called templates (since calling a template also
cannot be done through an AVT).
A bit awkward, but you don't lose the concept of an attribute set,
per se, you are just creating a dynamically callable version of one
rather than a pre-defined one.
I hope this helps.
I think so Ken.
How about a named template, param the @remap value,
read the external file of attribute sets, then copy over
the attributes explicitly and generates the output element
with all the attributes...
Long winded, but keeps the world tidy.
Bit messy with nested xsl:use-attribute-sets :-)
Thanks
--
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
--~------------------------------------------------------------------
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>
--~--