Interslavic is not part of MB language list, but on the release and work level I can choose [Artifical (other)].
The full name is “INTERSLAVIC COW - MEDŽUSLOVJANSKA KRÅVA - МЕДЖУСЛОВЈАНСКА КРӐВА” on YT (“English - Latin Interslavic - Cyrillic Interslavic”). I wanted to add these names as separate aliases and did it, but found I can’t set [Artifical (other)] for Interslavic aliases. What is the reason
Also: should I simplify the release and track title in any way or it is OK I kept all three names?
Basically, because international standards do not move as fast as human culture.
The Language field for a Release is documented as, “The possible values are taken from the ISO 639-3 standard.” There is apparently an ISO 639-3 code for Interslavic, but it seems it was only added in 2024. I don’t know how the distinction between Latin Interslavic and Cyrillic Interslavic is represented in ISO639.
It takes time for MusicBrainz developers to notice the change to ISO 639-3, and incorporate those changes into the MusicBrainz codebase. You could perhaps accelerate this by filing a bug ticket asking that isv be added to the list of MusicBrainz language codes.
I think ISO 639 is just for languages, not scripts, so wouldn’t the same ISO 639 code apply to Interslavic regardless of the script it’s written in? ISO 15924 is for scripts, though I vaguely remember there being some minor differences between that and what Unicode considers a script, like around Hrkt vs Hira/Kana. It looks like IETF language tag - Wikipedia combines language and script info.
That is a good point. Scripts and languages are not the same thing.
Nevertheless, the MusicBrainz documentation says that "…the possible values [of the Language field for a Release] are taken from the ISO 639-3 standard”. Until the MusicBrainz code changes, ISO 639-3 is our menu of language/script identifiers.
The release languages (and work lyrics languages, since it is the same list) are indeed ISO based. Most of the languages are actually in the database but hidden since they would clutter the list and have never been used - when a user requests one, we unhide it. Interslavic, since it was recognized in ISO so recently, was an exception and was not in our database at all yet, I added it now (and set the release as Interslavic).
That said, the question was about why a language is not in the aliases options. The aliases locales are locales, not languages nor scripts, and they follow DateTime::Locale - Localization support for DateTime.pm - metacpan.org which itself follows Unicode CLDR. That list is annoyingly restrictive (new locales are added by Unicode only if someone proposes them and champions them in some ways including adding a bunch of data and translations in that locale IIRC). We do update our locale list every once in a while (we are on CLDR 47 and 48 is now available so we maybe should update) but it will always be a lot smaller than the language list as long as we stick with CLDR.
