Bug 178278

Summary:	Umlauts treated case-sensitive in collection search
Product:	[Applications] amarok	Reporter:	cyrus_xiii
Component:	Collection Browser	Assignee:	Amarok Developers <amarok-bugs-dist>
Status:	RESOLVED FIXED
Severity:	normal	CC:	blaster999, cavesnow, echidnaman, pascal
Priority:	NOR	Keywords:	junior-jobs
Version:	2.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description cyrus_xiii 2008-12-20 14:36:54 UTC

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.

Comment 1 Jonathan Thomas 2009-01-30 20:32:50 UTC

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

Comment 2 Stefan 2009-02-09 00:42:07 UTC

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 :(

Comment 3 Seb Ruiz 2009-02-09 01:53:58 UTC

*** Bug 183743 has been marked as a duplicate of this bug. ***

Comment 4 Gennady Uraltsev 2009-02-09 01:59:01 UTC

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.

Comment 5 Gleb Litvjak 2009-02-20 10:42:55 UTC

Having the same issue with Amarok 2.0.1. When I search for "южный ветер", it does not find the "Южный ветер" track.

Comment 6 Myriam Schweingruber 2009-06-07 12:31:22 UTC

*** Bug 195514 has been marked as a duplicate of this bug. ***

Comment 7 cyrus_xiii 2009-06-24 16:22:04 UTC

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?

Comment 8 Mark Kretschmann 2009-06-25 13:49:34 UTC

Indeed, it seems fixed in SVN. Both uppercase and lowercase umlauts yield the same search results here.

Comment 9 Jonathan Thomas 2009-06-26 14:08:54 UTC

So I presume this will be fixed in Amarok 2.1.2?

Comment 10 Lydia Pintscher 2009-06-26 14:55:23 UTC

There is currently no plan for a 2.1.2 release. Next one will be alpha or beta of 2.2.