This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: using attribute value as an attribute name OR using element value as an attribute name
- From: David Carlisle <davidc at nag dot co dot uk>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Thu, 19 Sep 2002 17:25:55 +0100
- Subject: Re: [xsl] using attribute value as an attribute name OR using element value as an attribute name
- References: <10FBF97F828FD511B76300508B44B8470200483B@WCHQEX01>
- Reply-to: xsl-list at lists dot mulberrytech dot com
> The column ordering is a concern. The sort simply does an alphabetic
> sort. Somehow I need to apply the user's column selection order as well.
ah I was lacking meta markup. I did xsl:sort on name because that would
work for column1 column2 etc, I should have known they were not the real
names....
so actually I'd zap the key and instead do
<xsl:variable name="columns"
select="/root/config/columnList/column/@name"/>
....
<xsl:for-each select="row">
<xsl:variable name="row" select="."/>
<xsl:for-each select="$columns">
<xsl:value-of select="$row/@*[name()=.]">
untested as ever.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list