Hi all,
I want to thank everybody for their valuable contributions to this thread.
Compiled stylesheet modules were indeed a bit of topic.
My requirement was a single stylesheet file that was the result of
expanding all xsl:import statements
I ended up developing a stylesheet that looped over all the import
statements repeatedly,
in order to carefully group keys, parameters, functions and templates,
dropping the template match="/" from every stylesheet but the main
driver stylesheet
Since each of the imported files already had its functionality in
separate modes,
I could do this without much trouble
Thanks again for all suggestions
Geert
On 11/12/2007, Andrew Welch <andrew(_dot_)j(_dot_)welch(_at_)gmail(_dot_)com>
wrote:
> > It may be ideal for you, but it won't solve the OP's problem at all.
> > He will be in exactly the same situation as now.
>
> The OP said:
>
> "I have a stylesheet with a pipeline in it
> and a large set of imported stylesheets...
>
> I would like to deliver one expanded stylesheet."
>
> So the requirement is to be able to combine multiple stylesheets into
> a single deliverable...which "compiled stylesheet modules" would fit
> perfectly.
No it wouldn't. He wants one file, not several modules.
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--