George,
This is cool. Nicely done.
At 06:12 AM 3/23/2005, you wrote:
After sleeping on it I was able to answer my own question, however I suspect
that that p1 and p2 templates could be generalised to handle any named
parameter, but haven't figured that out yet.
How about
<xsl:template match='p' mode='parameters'>
<xsl:param name='caption'/>
<xsl:variable name="@name"/>
<xsl:value-of select='$caption/p[(_at_)name=$name]/@value'/>
</xsl:template>
Then you'd need
<caption key='Client not on file'>
<p name="client-no" value='123456'/>
<p name="priority" value='99'/>
</caption>
and
<target xml:lang='en'>Client number <p name="client-no"/> not on file.
Priority:
<p name="priority"/></target>
You've already done the hard part. Too bad the parameter names have to be
in one language. :-)
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>
--~--