Open User087 opened 3 years ago
I think I looked into it once, it turned out to be hard to detect which languages are even available, unless by managing a hard-coded list.
I think I looked into it once, it turned out to be hard to detect which languages are even available, unless by managing a hard-coded list.
Am I correct in thinking that's no longer an issue and that the available languages are now specified in "\share\locale"?
Even if no option is added to the GUI, can it at least be added as a command line argument to be passed to the executable? That can be more convenient to just pin the program to the start menu and modify the shortcut target by adding the command line switch at the end, instead of something comparitively convoluted like this method: https://netlicensing.io/blog/2012/06/15/set-environment-variables-in-windows-shortcut/ and having to explicitly change the icon etc.
I'm aware from #495 that you can run
set LANG=<lang code>
in a terminal and then launch the application from there, but have you considered just adding a setting in the GUI to set the language of the user interface for all future launches, rather than having to go throughset LANG=<lang code>
every time? Changing the interface language may be because a person prefers to use a different language to that of their system locale, not just to test out a new translation temporarily.