This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: XSLT FAQ? and really questions
- To: xsl-list at lists dot mulberrytech dot com
- Subject: Re: [xsl] XSLT FAQ? and really questions
- From: David Carlisle <davidc at nag dot co dot uk>
- Date: Fri, 20 Apr 2001 23:07:09 +0100
- References: <NEBBKGEKKAMIGFNJAALHGEPACJAA.jdenton@galdosinc.com>
- Reply-To: xsl-list at lists dot mulberrytech dot com
> This is a really great example.
actually it's a really bad example. Using disable-output encoding
completely misses all the benefits of using a transformation language
like XSLT which is designed to produce element nodes, not literal text.
I think you want something like
<xsl:stylesheet
version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>
<xsl:output encoding="utf-8" indent="yes"/>
<xsl:template match="/">
<idsets>
<ID1List>
<xsl:copy-of select="/records/record/ID1"/>
</ID1List>
<ID2List>
<xsl:copy-of select="/records/record/ID2"/>
</ID2List>
</idsets>
</xsl:template>
</xsl:stylesheet>
which produces:
BASH.EXE-2.02$ msxsl node.xml nodes.xsl
<?xml version="1.0" encoding="utf-8"?>
<idsets>
<ID1List>
<ID1>123</ID1>
<ID1>345</ID1>
</ID1List>
<ID2List>
<ID2>234</ID2>
<ID2>456</ID2>
</ID2List>
</idsets>
when run in the EE.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list