Note,
- even though we can select multiple secondary release group types, Style says you should only enable a type if it represents most of the tracks on the releases.
- even though we can select multiple lyrics languages, Style says you should only enable a language if it’s used for an extremely large percentage of the lyrics
Presumably, the reason for this is because we want these fields to serve as disambiguations between objects at the same level on the same artist, rather than simply indicating that some portion of the object is a thing. So I’d expect that a hypothetical schema change that allows an MB Release to indicate multiple text languages and scripts (rather than the fake and useless existing “multiple” option) should not mean that we select all scripts used in text of the tracklist if that’s not a reasonable representation of the tracklist as a whole and when compared against other tracklists in the same release group.