RE: Multiple output types and embedded documentation

["Pawson, David" <DPawson at rnib dot org dot uk>]

 David Carlisle 

>> If I'm right, this would be a 'weave' solution.
>> For documentation you'd run a stylesheet to pull the doc:
>> elements?
>
>that's weave, but for Warren's version, where the original file isn't 
>directly usable then you also need "tangle" to extract a runnable
>stylesheet from the documented sources.

<grin>So now we have the full suite, tangle, weave and trace</grin>
Hmm. Surely its untangle?

>> 1. How do you 'disable' output from the undesired namespaces
>>     when not in use.
>> 2. I don't understand the 'intermediate step' idea above.
>
>You'd do something along the lines of the following (ignoring
>attributes for now)
>
>when applied to the documented source, it copies xsl 
>namespaced elements
>throws away doc elements and out_1 elements, and moves any out_2
>elements into the xsl namespace.
>
>Thus the result would be a usable stylesheet without documenattion and
>using the "out_2" version of the code.

Kinda neat!

Anone else think this sounds like the best approach yet for the weave
solution?

Regards DaveP


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list