This is the mail archive of the
mailing list .
Re: xsl:include with plain text input
It's an option, but I was hoping to be able to create standalone documents.
The transformation is done hours or days before it is sent to the clients,
during which time the physical output file must be moved around.
If I must, I suppose I could put the <script> ... </script> at the start and
end of the script files, and include them as parsed entities. I was hoping
there was another solution.
On Thursday 14 February 2002 12:40, Ivan Rubin Ayma wrote:
> Just leaving the work of including the script to the client? :)
> > -----Mensaje original-----
> > De: Peter Davis [mailto:email@example.com]
> > Enviado el: jueves, 14 de febrero de 2002 17:33
> > Para: firstname.lastname@example.org
> > Asunto: [xsl] xsl:include with plain text input
> > I remember seeing this discussed in an article somewhere, but
> > now I can't
> > find it. My problem is that I have several plain text files
> > (*.js, which are
> > ECMAScript scripts) that I would like to output along with
> > the rest of my
> > stylesheet's output. <xsl:include> obviously doesn't work,
> > because it
> > expects a stylesheet as input. Are parsed entities capable
> > of accepting
> > plain text as input?
> > Thanks much for your help!
> > --
> > Peter Davis
> > You'll never see all the places, or read all the books, but
> > fortunately,
> > they're not all recommended.
> > XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
The American Dental Association announced today that most plaque tends
to form on teeth around 4:00 PM in the afternoon.
Film at 11:00.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list