Subject: Re: [xsl] N : M transformation From: David Carlisle <davidc@xxxxxxxxx> Date: Sat, 1 Feb 2003 10:56:32 GMT |
I asked for http://www.w3.org/TR/xslt20/#element-result-document aspart of a spec draft, as opposed to the various extensions. As far as I know saxon 7's the only experimental xslt2 system that's been "announced" Although mention of a xalan xslt2 system has been mentioned on this this list as well (check the archives) One should be very careful about using any such systems in production of course, XSLT2 is only a draft, and in particular the multiple output instructions have changed quite a bit over the XSLT2 drafts so there's no assurance that it will end up looking like it does currently. Using exslt's document extension or the processor specific mechanism provided by an XSLT1 system is to be prefered at present except for experimenting with the current draft specs. That said, a standard multiple-output mechanism in XSLT will be a very welcome addition, it's been clear since before XSLT1 REC was finished that this was perhaps the largest gap in the XSLT1 specified functionality and just about all processors have such an extension. The exception being msxml which can output multiple files but only if you don't need the customisation possibilities of xsl:output and can accept the default linearisation of the MS DOM's .xml method, and you are running msxml in an environment that has write access to the filesystem (not in a browser). Similarly mozilla doesn't do multiple output, as it doesn't have write access either. David XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] N : M transformation, Tobias Reif | Thread | Re: [xsl] N : M transformation, Tobias Reif |
Re: [xsl] New to XSL - invalid toke, David Carlisle | Date | [xsl] RenderX XEP Academic Edition , David Tolpin |
Month |