MediaMonkey forum

Accented and unaccented letters should be considered equal in a search (or a sort). Currently (version 3.0.3.1140) they aren't.

e.g. a search for "crevier" will not find "Crévier"

I have mentioned this since a while ago (Oct 2005) and still no luck in implementing it...maybe it's hard, maybe not many of MM users need it...

http://www.mediamonkey.com/forum/viewtopic.php?t=6233

Maybe if many people comment and wish for this the request could clim higher on the wishlist

I would love to see this implemented as well. It would be particularly useful for Classical as many composers and works have these accented characters. It is nice to have the accented characters tagged, but would not be very easy to use the character in routine searches. Thanks.

Yes, it should definitely be done!

A lot of languages have various different accents and it is not only accents but all sorts of diacritic signs that can alter the pronunciation or the meaning of a letter:

http://en.wikipedia.org/wiki/Diacritic

They are sometimes not possible or difficult to type(and many do not know how to do that) if you do not have the keyboard of the corresponding language. and even if it works, it is a different thing to type only once for tagging the songs and, on the other hand, having to type those accents/signs each time for the search. it is simply too annoying.


The main problem with the search in those cases is that some titles or artist names that should have diacritic signs are tagged correctly but others are not. Because of the typing difficulties diacritic signs in the tags or path are very often set wrongly in a grammtical way or they are not there at all.

That's why you normally want all those letters with diacritic signs in the search results as well when searching for the "base" ones, orherwise you may not be able to find those with accents/diacritic signs at all.

The developers should change that as proposed here as soon as possible.

Yes! Searchs & sorts should be both Case and Diacritic insensitive.

Please implement this in the next version! This is very annoying to work around!
Helpful example: Search for 'Dvorak' misses 'Dvořák'.

Yes! please please pretty please

If All goes well this is planned feature for MM 3.1 Final.

Peke wrote:If All goes well this is planned feature for MM 3.1 Final.

PLEASE make this optional. Diacritic-insensitivity would be great to have, but exact match is needed also.

That is why I said if all goes as planned.

Peke wrote:That is why I said if all goes as planned.

You made no mention of it being optional. Is your plan that it be optional?

Good to see this coming, been waiting for ages!

Thanks for the info Peke!

can somebody give us please some hint about the progress on the issue of this topic?....thanks