This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Multiple output types and embedded documentation
- To: xsl-list at mulberrytech dot com
- Subject: Multiple output types and embedded documentation
- From: Warren Hedley <w dot hedley at auckland dot ac dot nz>
- Date: Thu, 29 Jun 2000 13:35:41 -0400
- Organization: Department of Engineering Science, The University of Auckland
- Reply-To: xsl-list at mulberrytech dot com
We've had a bit of discussion recently on embedding documentation
within XSLT stylesheets that can then be extracted easily. In
addition to this, I have stylesheets which are largely identical
in logical structure, but produce different output depending on the
target format. Maintaining these has always been a pain. I'm now
thinking about making the entire thing a two stage process - this
is probably best explained with an example. Here's my documented,
multiple target, NOT FUNCTIONING, stylesheet.
<xsl:stylesheet xmlns:xsl="logic commands"
xmlns:doc="doc format"
xmlns:out_1="output type 1 (latex)"
xmlns:out_2="output type 2 (html)">
<xsl:template match="/">
<doc:h1>Root Element</doc:h1>
<doc:p>My root element doesn't really do anything useful.</doc:p>
<xsl:for-each select="*">
<out_1:value-of select="concat('\alltt{', ., '}')" />
<out_2:element name="code">
<out_2:value-of select="." />
</out_2:element>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
To then extract either documentation, or working stylesheets that
produce the output formats that I'm looking for, I apply more
general stylesheets.
* Does anyone like this idea?
* Has anyone already developed a solution along these lines?
* Does anyone have a better suggestion?
If people are interested, it might be worth trying to work out what
functionality is required, and produce a set of readily available
stylesheets to do that intermediate step.
--
Warren Hedley
Department of Engineering Science
Auckland University
New Zealand
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list