[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Multiple output types and embedded documentation
Warren Hedley Presumably, using this format, you would swap out the namespace of either out_1 or out_2 and replace it with the xsl namespace, to select the actual output wanted? If I'm right, this would be a 'weave' solution. For documentation you'd run a stylesheet to pull the doc: elements? >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. Questions: 1. How do you 'disable' output from the undesired namespaces when not in use. 2. I don't understand the 'intermediate step' idea above. Regards, DaveP >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. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
|
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
|