Programmers: there are good programmers, mediocre programmers, and bad programmers.
Most reasonably capable programmers would be using Unicode throughout their application, which would automatically support the world’s various alphabets. Capabilities are often limited by the inherent capabilities of the toolkits and libraries used, as well; injudicious selection of such can create application shortfalls like this. That could be an additional factor.
Roon sorts Andersson, Åkesson, Ärlingman the same, that A is the same as Å and Ä. That’s not true, A is in the besinning of the alphabet and Å + Ä is in the ed. I am so annoyed by that. All my music that contains Å Ä and Ö is sorted wrong.
A performance issue according to @brian but I think Roon is prioritizing other things and I guess the users that are active on this forum isn’t representative for the whole user group. How does Roon collect feedback from users in Andorra or Mongolia to see them Happy?
it would be interesting to know their current take on this - the post below is over three years old.
I work on search at roon and I wholeheartedly agree there is definitely room for improvement in how non-Ascii characters are handled, and it’s not being ignored. My own family name includes characters like č and ć, and I worked a lot with German content before, so I do understand the frustration about it.
Generally speaking, character normalization is done mostly for the convenience of the user, and not because English is preferred in one way or the other. Like @Chris_Rudmin mentioned in the case of searching with “bjork” should definitely yield “Björk”. “bodo” should yield “Bodø” as well.
On the other hand, the user typing in “Øst” without quotation marks should respect that and prioritize search results that are “closer” to the original search query.
@Thomas_Nielsen 's response is spot on about the deeper challenges regarding the wild west of metadata sources and transliteration.
Unfortunately, it’s not something that can be fixed overnight, but it’s quite high on the priorities list.
My given name is Njål, they are not special characters to me either, but to the average English speaker they are.
Just to make a point re A≠Å:
If I was to search for Agnetha Fältskog written with a Norwegian æ rather than Swedish ä, or Björn Ulvaeus with ø rather than ö, I would still expect to get the former Abba members (and Abba) as results, just after any music person actually named Bjørn Ulvaeus or Agnetha Fæltskog.
And don’t forget that there is a convention that names with the Scottish/Irish prefixes “Mac” and “Mc” should be sorted together, so “MacWilliams” comes after “McGlaughlin”, and in some collating schemes both may come before “Masters”.
Indeed, my point was just to make sure that when speaking of different letters to many users these are everyday letters. Although I must admit that å is very rarely used in Finnish, my native language. Ä and ö are very common and can be used in artist names or song names.
That might be nice sentiments - but Roon is a commercial organisation and this has to paid for. Roon does not offer Chinese, Cyrillic, Amharic or the multitude of Indian languages and their different alphabets.
It would be interesting to know what the locale settings are on the Mac and Nucleus. On Nucleus, presumably you could ssh to it and type “locale -v” to display the settings. Does this also work on Mac (in a Terminal window)? Don’t have one to try it with.
This would tell us what language and character set the computer thinks it is using.
Yes, they are part of your language. When we say ‘“special characters”, we mean letters not found in the 26 letter English alphabet. Although that is my language, I am sensitive to the fact that for billions, it is not, and that any language I can think of, other than English, has different letters either instead of, or in addition to, the 26 that English uses. I pray that Roon begins to address this shortcoming. (And the sooner, the better)