[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

AW: xsl:sort/@case-order feature missed

Subject: AW: xsl:sort/@case-order feature missed
From: "Nestel, Frank ISC 6" <nestefan@xxxxxxxxxx>
Date: Thu, 31 Jan 2002 17:07:32 +0100
case order xsl
> I only have the first edition of the XSLT programmer's reference,
> so maybe this has changed, but mine says for the meaning
> of case-order :
> "Defines whether upper-case letters are to be collated before
> or after lower-case letters. The default is language-dependant."

You are right, I looked only at the next (bottom of next page) and
not on the short description. Still haven't found that in the spec.

> If there was an uppercase() function (is there one in XSLT 2 ?)
> this would get you the desired order :
> <xsl:sort select="uppercase(...)" />

That would be a way, but won't work with XSLT 1.0. But since we
are speeking of preprocessed XMLs (they all pass thru an Java
preprocesser, this is a way to go).

> PS: I don't quite understand your point 2.
> Do you mean that my previous suggestion would not work in
> your application ? Notice that I carefully did not write such
> thing as :
>  <xsl:choose>
>  <xsl:when test="...">
>  <xsl:sort ...>
>  </xsl:when>
> Perhaps if we could see more of the templates in question
> it would be easier to help.
> In any case, the point is moot if as I surmise above, the
> absence of case-order does not give your intended result.

Yes, if everything is case ordered the question makes no sense.
But if you mind, the problem was somewhat like this:

<xsl:template match="...">
	<xsl:call-template name="template1">
	<xsl:call-template name="template1">
	<xsl:call-template name="template1">

<xsl:template name="template1">
	<xsl:param name="caseOrder"/>
	<xsl:call-template name="template2">
		<xsl:with-param name="caseOrder" select="$caseOrder"/>

<xsl:template name="template2">
	<xsl:param name="caseOrder"/>
	<xsl:call-template name="template3">
		<xsl:with-param name="caseOrder" select="$caseOrder"/>

<xsl:template name="template3">	
	<xsl:param name="caseOrder"/>
	<xsl:for-each ...>
		<xsl:sort case-order="{$caseOrder}"/>

All of those templates are complex and lengthy. And that is why it 
wouldn't have been nice to have different versions of the xsl:sort.
Of course it is only a matter of error prone redundancy, not of function.

Hope I explained the problem I have. Thank you for your patience.
But as it sounds your argument is valid and there is no sort without
case-order anyway.


> ----- Original Message ----- 
> From: "Nestel, Frank ISC 6" <nestefan@xxxxxxxxxx>
> To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, January 31, 2002 2:51 PM
> Subject: AW:  xsl:sort/@case-order feature missed
> > 
> > Thanks Jonathan for your reply.
> > 
> > I'm not sure if I understand your suggestions. Well, maybe
> > I understand but didn't like what you meant :-)
> > 
> > 1. When it comes to our application, I could use something
> > like "sort, but use document order as tiebreak" instead of
> > specifying a case order explicitely or implicitely (by
> > some default). If this order does not exist, I could use
> > it. Maybe we have to create an extra sort attribute or so.
> > But this is ugly. As I understand Michael Kay in his book,
> > he claimes that case order depends on the actual publication,
> > not only on language. What depends on language is the way
> > the letters themselves are collated (he gives an example
> > about the rules for German/Swedish &auml; ) In my eyes the
> > XSLT standard of w3c is not entirely explicit in this respect.
> > But this might be my lacking sense of fine grained English.
> > In XSLT 2 it all depends how to read "case-order effective value"
> > in the situation where no case-order is present. I didn't 
> understand 
> > yet the new collation attribute in XSLT 2 and whether this could 
> > provide a solution to my problem:
> > 
> > 2. Of course one could keep two sort statements. The problem 
> > I had only arrose, cause we had a stack of named templates 
> > which were all them same, but differed in that little 
> case-ordering, 
> > so duplication does not only involve duplication of two simple 
> > xsl:sort elements but restructuring and duplication of some part 
> > of a template call hierarchy. We just wanted to avoid that sheer 
> > uglyness. Unfortunately there is no way of doing s.th. like
> > <xsl:choose>
> > <xsl:when test="...">
> > <xsl:sort ...>
> > </xsl:when>
> > ...
> > </xsl:choose>
> > Such a control probably hurt the possibilty to avoid some
> > runtime work by smart preprocessing of the stylesheet on
> > first translation.
> > 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.