|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: dynamically applying templates
On Sep 15, 2004, at 2:05 PM, Wendell Piez wrote:
.... and add a template to match mods:mods (but notice I pulled the mode, imagining that the "bibliography" mode is to handle nodes in the config document. OK, this works fine when I am matching a cs:* template and then from there applying to mods:*. However, it doesn't work when I need to apply templates to a cs: child. For example, the cs:origin element here: <reftype name="book">
<title font-style="italic" after=", "/>
<creator>
<names form="full"/>
</creator>
<origin before="(" after="), ">
<place after=":"/>
<publisher/>
</origin>With this template ... <xsl:template match="cs:origin">
<xsl:param name="source"/>
<xsl:apply-templates>
<xsl:with-param name="source" select="."/>
</xsl:apply-templates>
</xsl:template>.... am I right that I am passing cs:origin as the source to the children, where I really need to be passing the original mods:mods source. A child looks like: <xsl:template match="cs:place"> <xsl:param name="source"/> <xsl:apply-templates select="$source/mods:originInfo/mods:place"/> </xsl:template> I'm not sure, but is this where tunneling should come in? And if yes, how do I actually use it in this context? Bruce
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|

Cart








