> In fact, we've always over the years gotten emails asking for *more*<br>
> specificity, which is why we recently switched the database to be<br>
> case-sensitive. People *want* to know when they have both AC-DC and<br>
> AC/DC so that they can fix their tags" (Jeff)<br><br>In deed, you just wrote the reason why I started thinking about sih1 - <a href="http://wiki.github.com/LukasLt/Collector">http://wiki.github.com/LukasLt/Collector</a> - and sih1 is one of main homework to do. I'm thinking about it as a plugin, as there will always be users with different opinions, how similar things is really similar.<br>
<br>Creating a world wide standard, well, would be great, but unless someone really big would start supporting this, its close to impossible. <br><br><br><br>> /Stripping punctuation works fine usually, but when I google e.g. "C++<br>
> memory allocation" that's what I want, not "C memory allocation"./<br>
><br>
> Also if you remove duplicated characters it's a confusion for the user<br>
> for example Madonna is written as *Madonna* (with two N's) not *Madona*.<br>
<br>Very important topic too. But in this case a few things should be taken into account:<br>* Music is not technical literature. Yes such method would su*k if it would be used on BAR codes etc.<br>* sih1 should not be visible to user in normal conditions, just the same, as Amarok doesn't show uniqueid<br>
* I couldn't find any artists that could have have same sih1, as most
artists uses uniques names, and its very unlikely that someone would
title himself as Maddona or Madonna2, so even if false collisions are
possible they would be rare.<br>* Amarok already uses LIKE %keyword% syntax, so if I'm looking for e.g. Don McLean and type in don, Madonna is also found ;)<br><br><br><br>On 01/11/2010 02:44 PM, Jakob Kummerow wrote:<br>
>> In fact, we've always over the years gotten emails asking for *more*<br>
>> specificity, which is why we recently switched the database to be<br>
>> case-sensitive. People *want* to know when they have both AC-DC and<br>
>> AC/DC so that they can fix their tags.<br><br>In this point have some points rising. <br>I think it is reasonable to want to have artists and track's names spelled as they are titled by the original author. Of course, there is problem, how to know what is real original spelling. Precedent could be used in most cases: 1 User edited tag manually, 2 The correct spelling was fetched from Internet. 3 First used (e.g. first variant added to DB (in case of case conflicts), 4 Directly form file id3<br>
<br><br><br><br>Talking about "case-sensitive" DB scheme (a bit off topic), i didn't cached the point why Amarok is using uft_bin (case sensitive) instead of utf_general_ci (case in-sesitive). They both allows to store AC/DC and ac/dc as separate records, so users, wanting case sensitive environment still can have both. But when using utf_bin tracks are read from DB, collation is being converted to utf_general_ci on the fly, and it doesn't add performance. If utf_general_ci would be used, such conversion would be needed only when writing. And Amarok does much more reads than writes ;)<br>
<br><br><br><br><div class="gmail_quote">2010/1/11 Jeff Mitchell <span dir="ltr"><<a href="mailto:mitchell@kde.org">mitchell@kde.org</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 01/10/2010 02:40 PM, Milot Shala wrote:<br>
> If this is about to be implemented in my opinion this feature should be<br>
> a user's choice.<br>
><br>
> I agree with John in:<br>
> /Stripping punctuation works fine usually, but when I google e.g. "C++<br>
> memory allocation" that's what I want, not "C memory allocation"./<br>
><br>
> Also if you remove duplicated characters it's a confusion for the user<br>
> for example Madonna is written as *Madonna* (with two N's) not *Madona*.<br>
<br>
<br>
<font color="#888888"><br>
--Jeff<br>
<br>
</font><br>_______________________________________________<br>
Amarok-devel mailing list<br>
<a href="mailto:Amarok-devel@kde.org">Amarok-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/amarok-devel" target="_blank">https://mail.kde.org/mailman/listinfo/amarok-devel</a></blockquote></div>