-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Preferences: language names are translated into current locale #628
Comments
When the user first starts Minigalaxy, their system language is used, though. I think we can assume that the user can read that. The drop down is just there to give the user the option to use another language if they prefer. |
I wanted to also reuse these constants during windows game installations to map languages supported by the installer to the one selected in minigalaxy's preferences for when the installer does not return locale ids but language names. |
The SUPPORTED_DOWNLOAD_LANGUAGES should contain all the languages GOG can have in their installers, but they might have added more. |
The problem is how they are named and used by the installer when passing the /LANG= command line option during installation. A lot of the installers themselves support multiple languages. Its not about the key used to download the installer (if that is used there). Either
Or
The first variant can easily be mapped and this is what lang_install currently does. |
Oh, I wasn't aware of that. Maybe we could add the lower case English names for languages to the lists as well, but that would require some refactoring. |
Isn't there an API where we could fetch the supported list of languages? That would be a more dynamic solution than just hard-coding all these values. |
When checking constants.py, i found that the value lists for language settings, SUPPORTED_DOWNLOAD_LANGUAGES and SUPPORTED_LOCALES, both pre-translate the titles used in the language selection combos into the current locale.
Nowadays such selection lists normally keep each entry in the respective selection's locale.
There's at least one reason for that: character sets. A language setting might accidentally have been set to another language with a character set that the user is not capable of reading. When all language names are also translated, finding and recovering the right setting might become a longer run of trial-and-error.
The text was updated successfully, but these errors were encountered: