Łukasz, Thanks for your comments. > Could you describe your current solution in more detail?
Well, my use of the term "solution" was perhaps a bit generous. First, I educated my users why this problem was hard to solve. Second, I picked a single collation that everyone could live with. Third, I used the locale module to sort on the application side, which, as you say, was slow. But because the data don't change much, I was able to cache the result to achieve acceptable performance. Even if application-side sorting is slow, nevertheless, in many cases that will be preferable to users not finding what they are looking for because the item doesn't show up where it "should." So it's a tradeoff between two aspects of user experience (speed vs. expected sort order). In many cases, that tradeoff would favor language-specific collation. My two cents. Ed. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
