See this comment in English Spelling Vs Japanese Spelling
So, I would not waste much time thinking about this particular guideline.
Thanks. I know about aliases and intensively use them. For all artists I am interested in I have added “artist name” and “legal name” aliases with proper locale.
However, I still have a problem.
Shortly, I can easily read names/titles written in Latin, Cyrillic, and Greek scripts. So, I do not want all artist names are transliterated to one language. Instead, I want all artist names written in scripts I understand are left intact, and only names written in scripts I cannot read (Japanese, Armenian, Hebrew, etc) are translated/transliterated to English.
Currently Picard tagger does not have such functionality, so I am working on Picard plugin. For a given artist, I have id, name, sortname, and list of aliases. If name is not in script I can read, then I search the list of aliases for a primary alias for desired locale and take name and sortname from it. If name is in script I can read, it sounds good — I have artist name without any searching, but actually I am in a trouble: I have sortname without any searching, but in case of non-Latin name sortname is Latin and so useless. Oops.
Let me think on a workaround. For the artist, I have a list of aliases for bunch of locales. There is (not more than) one primary alias for a locale. But it is not clear which locale is primary. Oops.
…“Sort Name” in the database. This is a useless column…
Artist’s sortname would be useful if it match name (i. e. written in the same script). Alternatively, one of primary aliases should be marked as “super primary”.