Creating JSON files to make localization easier

[IPeTeXI]

I think of it as having several JSON files for the different languages, and then you can simply change the language at the corresponding line in your config. Just like you can currently do with the rest of uosc, but unfortunately not with your custom elements. I think that would make it easier to support multiple languages in the future.

I would like to thank you for your efforts and would love to use the config in english or german while staying up to date with the main branch.

[dyphire]

Honestly this is difficult to implement, it's not just that different language files need to be switched in mpv.conf and input.conf (which should actually be possible with scripts). The bigger problem is that there are scripts that also need to switch between languages, and I can't think of a good way to handle that at the moment.

If anyone has ideas feel free to suggest them or open the appropriate PR.

[IPeTeXI]

Unfortunately, I'm not very skilled when it comes to GitHub and scripting. But I do try to tinker around from time to time.
Maybe we can do something similar to this:

Translation guide: https://github.com/Samillion/ModernZ/blob/main/docs/TRANSLATIONS.md

1. Loading the external locales: https://github.com/Samillion/ModernZ/blob/1be264dd4b48322aacccdad6989b6a02e017b395/modernz.lua#L359
2. Localized menu entries: https://github.com/Samillion/ModernZ/blob/1be264dd4b48322aacccdad6989b6a02e017b395/modernz.lua#L304
3. Summarized locales: https://github.com/Samillion/ModernZ/blob/1be264dd4b48322aacccdad6989b6a02e017b395/extras/locale/modernz-locale.json

I'm not sure if that's all there is to the logic, but I think it's the majority of it. 2. Will probably be the most difficult to implement or the most time-consuming.

[dyphire]

it's not just that different language files need to be switched in mpv.conf and input.conf (which should actually be possible with scripts).

Unfortunately after testing this was found to be impossible. Although mpv allows configuration files to be changed at runtime using the load-config-file and load-input-conf commands, it does not provide the corresponding configuration file properties for observing their changes. This made it impossible for third-party menu-like scripts (like uosc) to synchronize configuration file changes for dynamic updates, meaning that the whole idea of localization was aborted.