Version: 2.0 (using Devel) OS: Linux Installed from: Compiled sources Umlauts are treated case-sensitive in collection search, hence several expected entries do not show up in the results (e.g. "ärzte"). Only tested with umlauts commonly used in German.
I can reproduce this with Amarok 2.0.1.1. For reference, we've also received a bug report at Kubuntu regarding this: https://launchpad.net/bugs/320305
Can't reproduce this with amarok-2.0.1.1 on Gentoo. Tried to use "ärzte", too ;) But i can't play tracks, which have umlauts in their filename :(
*** Bug 183743 has been marked as a duplicate of this bug. ***
I have found a discussion of something very similar but that happened about two years ago with a previous version of amarok: Bug 138482. They talk about some kind of sql search function incorrect implementation. I am no expert, but the symptoms seem exactly the same so, even though it seems that amarok doesn't use the same sql db server or whatever maybe the same solution is applicable in this case.
Having the same issue with Amarok 2.0.1. When I search for "южный ветер", it does not find the "Южный ветер" track.
*** Bug 195514 has been marked as a duplicate of this bug. ***
While the issue remains with the latest stable version (2.1.1), a recent developer blog post regarding imporved UTF-8 support has me hoping that this bug may already be resolved. http://amarok.kde.org/blog/archives/1068-UTF-8-and-Your-Music.html Could someone with a recent build try to verify?
Indeed, it seems fixed in SVN. Both uppercase and lowercase umlauts yield the same search results here.
So I presume this will be fixed in Amarok 2.1.2?
There is currently no plan for a 2.1.2 release. Next one will be alpha or beta of 2.2.