-
Improvement
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
How does MusicBrainz envision alternate tracklists utilizing existing language/script data, if at all? (MBS-4501, MBS-2544) Is the ideal purpose of language/script to disambiguate tracklists from each other? Or is the purpose of language/script to quiz users on their math skills?
e.g., VGMdb has "Japanese" and "English" tracklists that don't depend on math skills, and it makes sense to most people - less than 10% of a tracklist needs to use Japanese to be considered Japanese here: https://vgmdb.net/album/4494. If MusicBrainz applied math to these tracklists, both would be marked "English/Latin" and the fields would serve no purpose. The only logical use case of the fields IMO is to disambiguate the tracklists.
- has related issue
-
MBS-13200 Allow entering several languages/scripts for a release
- Open