Subject: RE: [xsl] Parameter in "xsl:include" From: "Michael Kay" <mhkay@xxxxxxxxxxxx> Date: Thu, 8 Feb 2001 18:46:12 -0000 |
This sounds like a case for using XML entities to me: <xsl:include href="&common;/template1.xsl"/> Alternatively depending on your processor you could set up a URIResolver to resolve the URL externally. Mike Kay > -----Original Message----- > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of > Martin Renner > Sent: 08 February 2001 16:13 > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: [xsl] Parameter in "xsl:include" > > > Hi. > > > No. (FAQ). xsl:include is a compile-time facility, not > run-time. Explain > > your problem, and someone will tell you the right way of solving it. > > Cool service :-) > > I have several XSL files which have some parts in common. So > I would like to put > those common parts (three different "xsl:template match" > blocks) in three different > files which can be included as needed. > > The XSL files, which will include the common files, are > structered within subdirectories. > > To make the use of the includes less error-prone, all > include-statements should look > the same (so someone can use copy&paste). > > e.g. something like > > file1: include "$common/template1.xsl" > sub1/file2: include "$common/template1.xsl" > > instead of > > file1: include "../common/template1.xsl" > sub1/file2: include "../../common/template1.xsl" > > The parameter "$common" is already set to the correct > directory. It's just that I > cannot use it in xsl:include. > > > Martin > > > > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Parameter in "xsl:include, Martin Renner | Thread | RE: [xsl] i18n approach, Dylan Walsh |
RE: [xsl] Passing parameters to fun, Michael Kay | Date | Re: [xsl] How to navigate in an exp, David Carlisle |
Month |