This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: RE: external files
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: Re: [xsl] RE: external files
- From: "Tamre2" <Tamre2 at msn dot com>
- Date: Sun, 29 Jul 2001 15:38:14 -0700
- Organization: Microsoft Corporation
- References: <005501c10990$8fb578e0$c4343c3e@PCUKMKA>
- Reply-To: xsl-list at lists dot mulberrytech dot com
----- Original Message -----
From: Michael Kay <mhkay@iclway.co.uk>
To: <xsl-list@lists.mulberrytech.com>
Sent: Tuesday, July 10, 2001 2:59 PM
Subject: [xsl] RE: external files
> > I need to import an external file specified in my XML source
> > into the output
> > of my XSL transform. Ideally I would like to subject this
> > external file to a
> > seperate, source-specified XSL transform before piping it
> > into the output
> > stream. How can I best get this done?
>
> Is the external file XSL silly?
>
> You'll need to do some scripting of some kind, and the details will depend
> on your processor. With TrAX (=JAXP 1.1) I might tackle it by loading the
> document using the document() function, and writing a URIResolver to do
the
> separate transform before handing over the result.
>
> Alternatively since you are copying the external file unchanged, you could
> include it at the serialization stage: many processors have a SAX
interface
> between the transformer and the serializer, so you can put a SAX filter in
> between to modify the data stream at this stage.
>
> Mike Kay
> Software AG
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list