We keep having arguments about what the right language and script is for multi-language and multi-script releases, because some people prefer the most used language and script (even if it's English/Latin), some prefer whatever is not English/Latin to help differentiate from transl(iter)ations, and pretty much noone likes the (theoretically most appropriate) "multiple languages"/"multiple scripts" option since it doesn't say anything about which languages and scripts those are.

This has already been solved ages ago for lyrics languages on works, where we support multiple languages in one list and just list every language. There's no reason, as far as I can tell, why this couldn't be done for release languages and scripts, and it seems to be by far the most information-rich option.

This would require moving "language" and "script" from columns in "release" (and the yet unused "alternative_release") to tables "release_language" and "release_script" (and possibly "alternative_release_language" and "alternative_release_script" unless we choose to store both in one table with a boolean marker), in the same way we already do for "work_language".