(The problem still exists to some extent with xsl:result-document
in 2.0, but the inheritance structure in 2.0 is more flexible than that in
saxon:output.)
I don't understand what you mean by this. I have nested two
xsl:result-document elements in an XSLT 2 document - the outer one has
doctype-public and doctype-system attributes. The inner one doesn't have
these attributes and the file created by the inner one doesn't inherit the
doctype from the outer one which is the behaviour I'm looking for. I'm using
Saxon 8.x
So where exactly does the problem still exist and are there any potential
pitfalls in using this methodology?
From: "Michael Kay" <mike(_at_)saxonica(_dot_)com>
Reply-To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Subject: RE: [xsl] xslt 1.1 xsl:document
Date: Tue, 7 Nov 2006 14:13:55 -0000
The xsl:document instruction in Saxon 6.5.x was really more a renaming of
the previous saxon:output extension than a true implementation of what was
in the working draft of XSLT 1.1 (which never reached a stable enough state
to be implementable).
Unfortunately there's no explicit value for doctype-system or
doctype-public
that says "none", which means that if you've specified a value at one
level,
you can override it another level with another explicit value, but you
can't
cancel it. (The problem still exists to some extent with
xsl:result-document
in 2.0, but the inheritance structure in 2.0 is more flexible than that in
saxon:output.)
The only suggestion I can make is either (a) output the .ssi file at the
top
level of the transformation, or (b) run a second transformation on it to
get
rid of the unwanted doctype. Or of course (c) move forward to a more stable
version of the technology.
Michael Kay
http://www.saxonica.com/
> -----Original Message-----
> From: tom tom [mailto:tomxsllist(_at_)hotmail(_dot_)com]
> Sent: 07 November 2006 12:41
> To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
> Subject: [xsl] xslt 1.1 xsl:document
>
> I am using XSLT 1.1. I am attempting to use the xsl:document
> function to generate an html '.ssi' file to be included in
> other pages.
>
> I am unable to prevent this file from outputting a doctype
> declaration. It seems to be inheriting it from a parent
> xsl:document element - ie the xsl:document element exists
> inside of another xsl:document element which needs to output
> a doctype. When it does not sit inside of another
> xsl:document element there are no problems with the doctype.
>
> I am using saxon 6.5 and its a legacy system so can't be upgraded.
>
> Does anyone recognise anything I have described and do you
> know of a way to prevent the DOCTYPE declaration from displaying?
>
> _________________________________________________________________
> Windows LiveT Messenger has arrived. Click here to download
> it for free!
> http://imagine-msn.com/messenger/launch80/?locale=en-gb
>
>
> --~------------------------------------------------------------------
> 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(_at_)lists(_dot_)mulberrytech(_dot_)com>
> --~--
>
--~------------------------------------------------------------------
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(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
_________________________________________________________________
Windows Live? Messenger has arrived. Click here to download it for free!
http://imagine-msn.com/messenger/launch80/?locale=en-gb
--~------------------------------------------------------------------
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(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--