My main point is that the user who visits my site does not care about python, Unix, NT or any wierd metaphors about kettles. They want information fast and most users expect case insensitive sorts. Its simpler and easy. I think having the ignore_case option for a -tree and -in helps Zope by increasing the ease of development and friendliness to the user. -- Andy McKay, Developer. ActiveState. ----- Original Message ----- From: "Casey Duncan" <cduncan@kaivo.com> To: "Andy Dawkins" <andyd@nipltd.com> Cc: <zope-dev@zope.org> Sent: Wednesday, January 03, 2001 8:17 AM Subject: Re: [Zope-dev] case insensitive sorts
Andy Dawkins wrote:
Your analogies imply that this behavior is a bug or an unintended flaw in the design. I would argue that it is intentional. Unix file systems work the same way. Try doing an "ls" with mixed case files and you'll see what I mean.
It isn't a flaw. It seems as though it was overlooked.
The sort on text works by sorting the data by its ascii value. Capital letters have a lower ascii value than lower case letters. i.e. A-Z = 65 - 90 a-z = 97 - 122
The arguement is that the sort should probably go.... AaBbCcDdEeFf.....etc
-Andy
My point is that the sorting is intentionally Unix-like and case sensitive on purpose. Not due to laziness. But, perhaps the reason Unix is like that to begin with is due to laziness anyhow 8^). We'll never know for sure.
-- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )