StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><strong>Here is a generic, simple and not long (60 well-formatted lines) solution</strong>.</p> <p><strong>Sorting is performed on</strong> <em>all</em> <strong>wanted attributes and this doesn't require any manual duplication of templates</strong>:</p> <pre><code><xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:my="my:my" exclude-result-prefixes="my"> <xsl:output omit-xml-declaration="yes" indent="yes"/> <xsl:param name="pSortTypes" as="element()*"> <attr name="name" type="alpha" maxLength="15"/> <attr name="row" type="numeric" maxLength="6"/> <attr name="col" type="numeric" maxLength="4"/> <attr name="tabindex" type="numeric" maxLength="2"/> <attr name="sequence" type="numeric" maxLength="3"/> </xsl:param> <xsl:template match="*"> <xsl:copy> <xsl:copy-of select="@*"/> <xsl:apply-templates select="*"> <xsl:sort select="my:OrderedAttributeTuple(.)"/> </xsl:apply-templates> </xsl:copy> </xsl:template> <xsl:function name="my:OrderedAttributeTuple" as="xs:string"> <xsl:param name="pElem" as="element()"/> <xsl:variable name="vResult" as="xs:string*"> <xsl:apply-templates select="$pSortTypes"> <xsl:with-param name="pElem" select="$pElem"/> </xsl:apply-templates> </xsl:variable> <xsl:sequence select="string-join($vResult, '')"/> </xsl:function> <xsl:template match="attr"> <xsl:param name="pElem" as="element()"/> <xsl:variable name="vVal" select= "string($pElem/@*[name() eq current()/@name])"/> <xsl:variable name="vPad" as="xs:string*" select= "for $cnt in xs:integer(@maxLength) - string-length($vVal), $i in 1 to $cnt return '.' "/> <xsl:variable name="vPadding" select="string-join($vPad, '')"/> <xsl:variable name="vTuple"> <xsl:sequence select= "if(@type eq 'alpha') then concat($vVal, $vPadding) else concat($vPadding, $vVal) "/> </xsl:variable> <xsl:sequence select="string($vTuple)"/> </xsl:template> </xsl:stylesheet> </code></pre> <p><strong>When this transformation is applied on this XML document</strong>:</p> <pre><code><items> <item row="5" col="9"/> <item name="d" row="20" col="12" tabindex="" sequence=""/> <item row="1" col="5" /> <item name="d" row="5" col="6" /> <item name="a" row="7" col="8" /> <item name="s" row="1" col="5" tabindex="3" sequence="4"/> <item name="s" row="3" col="3" tabindex="3" sequence="4"/> <item name="c" row="5" col="9"/> <item row="2" col="5" /> <item row="20" col="9"/> <item row="0" col="9"/> <item name="s" row="3" col="3" tabindex="1" sequence="2"/> <item name="s" row="2" col="10" tabindex="1" sequence="2"/> <item name="z" row="8" col="15" tabindex="" sequence=""/> </items> </code></pre> <p><strong>the wanted, correctly sorted result is produced</strong>:</p> <pre><code><items> <item row="0" col="9"/> <item row="1" col="5"/> <item row="2" col="5"/> <item row="5" col="9"/> <item row="20" col="9"/> <item name="a" row="7" col="8"/> <item name="c" row="5" col="9"/> <item name="d" row="5" col="6"/> <item name="d" row="20" col="12" tabindex="" sequence=""/> <item name="s" row="1" col="5" tabindex="3" sequence="4"/> <item name="s" row="2" col="10" tabindex="1" sequence="2"/> <item name="s" row="3" col="3" tabindex="1" sequence="2"/> <item name="s" row="3" col="3" tabindex="3" sequence="4"/> <item name="z" row="8" col="15" tabindex="" sequence=""/> </items> </code></pre> <p><strong>Do note</strong>:</p> <ol> <li><p><strong>Sorting is performed on</strong> <em>all</em> <strong>attributes specified in an external parameter</strong> (<code>$pSortTypes</code>). Compare this to the currently accepted answer, which only sorts on <code>@name</code> and <code>@row</code> and requires hardcoding of the order and sort data-type.</p></li> <li><p><strong>The exact wanted sorting order of the attributes can be specified</strong>. It is their order as in <code>$pSortTypes</code>.</p></li> <li><p><strong>The sort data-type for each attribute is specified</strong> in the <code>type</code> attribute in <code>$pSortTypes</code> (currently just <code>"alpha"</code> and <code>"numeric"</code>)</p></li> <li><p><strong>The maximum length of the string representation of the value of an attribute is specified</strong> as the <code>maxLength</code> attribute in <code>$pSortTypes</code>. This is used for correct padding/alignment and also increases the sorting efficiency.</p></li> <li><p><strong>This demonstrates how to solve even the most complicated sorting problems by having a user-defined <code>xsl:function</code></strong> (in this case <code>my:OrderedAttributeTuple()</code>) that generates a single sort key.</p></li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload