Okay, here's the deal: I have several XSL stylesheets that do 
different things [obviously] but use a couple of templates that are 
common to more than one stylesheet and are thus kept in separate 
"include" files. The choice of additional template to be included 
depends on a few other factors that have to do with the specificities 
of my system, and that would take a long time to explain but probably 
wouldn't add much to this discussion.



All XML files are generated by PHP scripts; when an XML file is 
generated, the script inserts an xml-stylesheet PI indicating which 
ready-made XSL file is to be used for transformation. That XSL file, 
in turn, calls (includes) another XSL file containing the additional 
template(s).



For practical reasons, I have to rely on browser-based XSL 
transformation. As I cannot use PHP's XSL processor, I can't have PHP 
pass the URI of an include file as a parameter to the XSL file, which 
I imagine would work.



Any suggestions are welcome. And if anyone thinks my whole idea is 
stupid and that there would be a much simpler way to accomplish what 
I want, feel free to say so bluntly.



 




Could you include all the files that you could possibly need and then 
use the templates as necessary?

How much XSLt are you planning on including?



As an aside, I have one project which uses php/sablotron and it work 
fine for server-side transformations.



-Brian



Erik



--+------------------------------------------------------------------
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@xxxxxxxxxxxxxxxxxxxxxx>
--+--