[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

AW: [xsl] Sorting Upper-Case first. Microsoft bug?


Subject: AW: [xsl] Sorting Upper-Case first. Microsoft bug?
From: Markus Abt <abt@xxxxxxxx>
Date: Tue, 5 Aug 2003 18:17:06 +0200

Hi Mukul,
hi David,

in the example, Mukul gets A before a, but A4138 after a4136 when
case-order is upper-first.
I'm absolutely sure that MSXML and Xalan don't try to find integers
in text strings (unless told to do so).

You may try sorting Ac and ab to make this topic clear.
There are no integers in these, but the sorting will be ab before Ac,
even with upper-first sorting.

The sorting is done *lexicographically*, not binary or numerically.
In a dictionary I would expect xPath, XPath, and Xpath
always sorted before XSLT, xslt and Xslt.


Regards,
Markus

__________________________
Markus Abt
Comet Computer GmbH
http://www.comet.de



----------
Von: 	Mukul Gandhi
Gesendet: 	Dienstag, 5. August 2003 16:44
An: 	xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Betreff: 	Re: [xsl] Sorting Upper-Case first. Microsoft bug?

Hi David,
  The spec says that "if data-type is text, the sort
keys should be sorted lexicographically". How you are
describing (or, interpreting) it is correct.. 

i have observed that both MSXML and Xalan interpret
this clause in a certain way, when integer(s)
characters exists in strings. When the strings have
*all alphabets* (either small case or upper-case), how
you have described lexicographic sorting is being
implemented by both MSXML and Xalan .. But when
*integer characters* come in the strings, the
behaviour of processors becomes different..

i have observed that A4138 will come after a4136 , if
case-order is upper-first.. But if the strings were
lets say A and a, then A would come before a if
case-order is upper-first..

[...]

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



Current Thread
Keywords