Version: (using KDE KDE 3.4.0) Installed from: Fedora RPMs OS: Linux Sort order of files is not correct when using case insensitive sorting. Create a new directory with three files: Apple.i AppleBerry.i AppleOrange.i When sorted with case-insensitive sort, the order is: AppleBerry.i Apple.i AppleOrange.i I can see no reason why these would be sorted in this order (either case-sensitive or case-insensitive). Case-sensitive sort seems to work correctly.
I can't confirm. It is working fine here. What is your LANG set to?
LANG is en_US.UTF-8 -d Thiago Macieira wrote: [bugs.kde.org quoted mail]
Created attachment 11191 [details] screenshot showing sort order bug Hi, I have a similar problem. See attached screenshot: The names all start with "drossel", but are not sorted at all (in a way). drossel+anker+... is first, then one with "-": drossel_anker.... then another with "+" drossel+anker.... etc. This seems not to be sorted at all, at least regarding special characters (as in "+", "_" here). Thanks for investigating this ;) Jens
I suppose this is related to Bug 61989. The solution was that it is caused by behavior of strcoll() in some locales and perhaps is even a feature. I myself have LANG=en_GB.UTF-8 LC_CTYPE="en_GB.UTF-8" and also have this problem. Mischa
You could try export LC_COLLATE=C This way strcoll() behaves better.
*** Bug 104689 has been marked as a duplicate of this bug. ***
I can confirm this wrong behaviour. One example from my music folder (there are many others) - Konqueror sorts the names as follows: ... Chic - Good Times.mp3 Chicken Shack - I Rather Go Blind.mp3 Chic - Le Freak.mp3 It looks like Konq ignores all spaces and special characters and takes only letters and numbers into account when sorting. Btw: Other file managers, like Nautilus or Rox filer and even ls in a terminal, also show the files in the same wrong order.
Can those who have reproduced this problem please see if 'ls' shows the same sort order, and whether LC_COLLATE=C helps (as described in comment #5). It sounds like this isn't a KDE bug
Has anyone tried the suggestion in comment 8?
Feedback timeout, but please reopen this report if you have the answers to the questions in comment 8