-
Notifications
You must be signed in to change notification settings - Fork 668
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
Setup translations before Application
instantiation
#11142
Comments
This will also allow us to translate the help text. |
We can move this code to the
We can make this work, but it won't be the most elegant piece of code: we would have to move the command-line parsing and the language setup into its own function, just to prevent blowing up the See also issues #11245 and #11246 , which ask for the removal of both option. |
Now the messages during early start-up can be localized. Fixes: #11142
Now the messages during early start-up can be localized. Fixes: #11142
Now the messages during early start-up can be localized. Fixes: #11142
Steps to test:
|
Command line options are translated to the client UI language ❓ Tested on: steps:
cc: @erikjv |
That was the intended behaviour. |
Are the following step valid if translating command line options based on client UI language is the expected behaviour?
|
The order of trying to load translations is:
So both the UI language and the language for the help options should be the same, if there is a translation available for the options. If a string is not translated, the English version is shown. |
Tested on:
The help option and desktop UI texts are in the same language. ✔️ |
The version checks have translatable text, and are shown before the translations are set up. Move this to somewhere early in the
main()
function.The text was updated successfully, but these errors were encountered: