Version: (using KDE KDE 3.5.6) Installed from: Ubuntu Packages OS: Linux If you enter a tag like 'åäö', it will appear before tags beginning with an 'a' in the tag list, but it should appear last (åäö are last in the swedish alphabet). I'm guessing the same would happen for other non-english characters like ü.
Are you sure your locale is set to Swedish?
I switch between english and swedish locales often, and to produce the åäö characters you must be in the swe (or other language that uses them). So I've been in both locales, the tags are not sorted correctly in neither. But regardless it should not matter which locale you are currently in for the sorting to work, should it?
Sorting depends on locale, it is special knowledge that å is the last letter, in German ä is sorted like ae. I will have a look where the sorting is done and how to make it locale-aware.
Would be wonderful :) Here are some hints for a few scandinavian languages: swedish and finnish: ...xyzåäö norwegian and danish: ...xyzæøå
I have now found out that Qt provides sorting based on locale. When I start digikam with LAND=de_DE@euro set, "Ö" is sorted like "O" (OT: which as I learned is one valid variant of sorting, though I prefer sorting like oe), when I start with no lang set, it is sorted in front of all others.
Marcel, What's the issue for this files ? Gilles Caulier
We are using localeAwareCompare(), and that's about all we can do. The rest depends on Qt and the set locale. As I tested in #5, it works for me if the LANG (LANG, not LAND as above) is set correctly.
Marcel, This is want mean than only a QT4 Model/View for all folder view can improve this issue with KDE4 port. Right ? Gilles Caulier
Since this is a Qt specific issue (or am I wrong?), we could close this bug... Andi
Andi, Yes and no, because we will need to take a care about sorting when Album tree view will be ported to Qt4 Model/view. Gilles
Andi, Another candidate for Qt4 Model/View stuff Gilles Caulier
Closing some old bugreports that are related to old digiKam version, and that have not received answers for two years now. If you think the reports are still valid, feel free to re-open them, but please provide updates and do not just open them without giving feedback.
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier