The fix for defining additional translations might just be to merge multiple locale files.
en.mse-locale wants to only define the UI Strings, but right now is also being burdened with the overrides for within packages. The change mentioned in #41 was meant to push that responsibility to the packages, but it goes a bit far with that (and is incomplete) because some level of hierarchy lookup would still be valuable.
We can push some of those definitions into the game, but that still isn't a great solve. So maybe just independent locales is worth doing. The current *.mse-locale format uses the package name for defining the language, so maybe a different package type like an *.mse-sublocale or something stupid with the file having to define a locale key to append to.
The fix for defining additional translations might just be to merge multiple locale files.
en.mse-localewants to only define the UI Strings, but right now is also being burdened with the overrides for within packages. The change mentioned in #41 was meant to push that responsibility to the packages, but it goes a bit far with that (and is incomplete) because some level of hierarchy lookup would still be valuable.We can push some of those definitions into the game, but that still isn't a great solve. So maybe just independent locales is worth doing. The current
*.mse-localeformat uses the package name for defining the language, so maybe a different package type like an*.mse-sublocaleor something stupid with the file having to define a locale key to append to.