This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: xsl:element
- To: "'xsl-list at mulberrytech dot com'" <xsl-list at mulberrytech dot com>
- Subject: RE: xsl:element
- From: "Selva, Francis" <Francis dot Selva at purchasepro dot com>
- Date: Fri, 14 Apr 2000 12:43:40 -0700
- Reply-To: xsl-list at mulberrytech dot com
What I mean by that is when I use my saxon I use it like this.
saxon -o eg.html eg.xml eg.xsl
where eg.html is the output file.If I have the xsl:output
method="xml" then my output file extension should be xml right?.Cause thats
when it is displayed like <year>2000</year> if I have xsl:element.
Francis
*****************************************************
The woods are lovely,dark and deep.
But I have promises to keep,
And miles to go before I sleep
And miles to go before I sleep.
*****************************************************
> -----Original Message-----
> From: David Carlisle [mailto:davidc@nag.co.uk]
> Sent: Friday, April 14, 2000 7:24 PM
> To: xsl-list@mulberrytech.com
> Subject: Re: xsl:element
>
>
>
> > Well I have to have the output as an xml file for getting
> the output from
> > xsl:element.right?
>
> I don't know what you mean, but probably the answer is no.
> xsl:element produces an element node. That will produce XML or HTML
> markup for an element depending on the output type, and will produce
> nothing at all in the text output type.
>
> David
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
>
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list