Subject: Re: [xsl] unparsed text From: DaveP <davep@xxxxxxxxxxxxx> Date: Fri, 16 Nov 2012 15:21:48 +0000 |
The other thing worth mentioning is the 'default initial template' in 3.0.... what was the end result there?
3.0 will provide a default initial template, which you get by naming the template xsl:initial-template. However, since the XSLT spec doesn't define APIs, the exact effect depends on the API design. On the Saxon command line I'll probably change it so -it without an option value means -it:xsl:initial-template.
ahh xsl:initial-template, I like it, much better than default-initial-template="main" : )
Regarding the api, is it possible to not need the -it switch at all, and just always start with the xsl:initial-template if its present?
I see it as replacing initial template and mode altogether, much cleaner to just have a single entry point and go from there based on parameter values.
-- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] unparsed text, Michael Kay | Thread | Re: [xsl] unparsed text, Ihe Onwuka |
Re: [xsl] unparsed text, Michael Kay | Date | [xsl] Replace(//text()) in XSLT 1, Nathan Tallman |
Month |