I believe that 5.2 included a reasonably recent version of Saxon 6, which
claimed to support most of EXSLT, though it doesn't specifically list the
"document" extension element.
It does support xsl:document, which is only available if you mark your
style sheet as being XSLT 1.1, though that's probably best avoided, as XSLT
1.1 never saw the light of day, having been abandoned for XSLT 2.0.
Instead, you can use saxon
utput, which has basically identical
attributes and behavior to xsl:document and, I suspect, pretty close to the
EXSLT version.
All that said, one problem I've run into with generating multiple result
documents with various XSLT engines has to do with how the engine is used
by the application running it. Any sort of output-oriented capabilities of
the engine require that the engine itself handles writing the results to
disk. If the application calling it (Editor, in this case) just has the
engine do an in-memory transformation and handles writing the results to
disk itself, the features supported by the engine may not be available. I
don't recall if this is an issue with Editor and may depend on how you are
invoking the transform.
Let us know how it goes...
-Brandon
On Fri, Jun 29, 2012 at 4:42 PM, Hendricks Trevor <
-> wrote:
> You should be able to use the EXLT extension set with 1.0 to get the
> result document setup you're looking for. Try this link as a start.****
>
>
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Carolyn Herlin [
claimed to support most of EXSLT, though it doesn't specifically list the
"document" extension element.
It does support xsl:document, which is only available if you mark your
style sheet as being XSLT 1.1, though that's probably best avoided, as XSLT
1.1 never saw the light of day, having been abandoned for XSLT 2.0.
Instead, you can use saxon
utput, which has basically identicalattributes and behavior to xsl:document and, I suspect, pretty close to the
EXSLT version.
All that said, one problem I've run into with generating multiple result
documents with various XSLT engines has to do with how the engine is used
by the application running it. Any sort of output-oriented capabilities of
the engine require that the engine itself handles writing the results to
disk. If the application calling it (Editor, in this case) just has the
engine do an in-memory transformation and handles writing the results to
disk itself, the features supported by the engine may not be available. I
don't recall if this is an issue with Editor and may depend on how you are
invoking the transform.
Let us know how it goes...
-Brandon
On Fri, Jun 29, 2012 at 4:42 PM, Hendricks Trevor <
-> wrote:
> You should be able to use the EXLT extension set with 1.0 to get the
> result document setup you're looking for. Try this link as a start.****
>
>
>
> ** **
>
> ** **
>
> ** **
>
> *From:* Carolyn Herlin [
