Hi Abel,
Thanks for answering
I assume you'd want the expanded stylesheet to obey the import
precedence rules?
Correct, and I know it is not trivial
and I am not sure this can be done with a stylesheet
I assume there is some complex processing involved
If you know of one specific set where the precedence is apparent
(i.e., only on the / match, and the rest is inside the modes you
mention), perhaps an if/when like construct in your main
concatenated stylesheet would suffice.
I was already thinking in those terms
I just have to drop all the serialization information
and deal with the templates with match="/"
... I could simply not copy them over
I just wanted to make sure there isn't a simple tool available somewhere
(I could always try to compile the stylesheet)
May I ask why you want them all together? It seems to me that
separate logical units is a better approach than one big stylesheet.
Correct, I will maintain them separately of course,
but my customer has to fit the chain in, in an application that is
not to be touched.
I will deliver in seperate stylesheets, but I would like to have some
backup if the importing should fail, caused by path issues eg.
(I have no control over the execution environment)
cheers
Geert
Cheers,
-- Abel Braaksma
--~------------------------------------------------------------------
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>
--~--