Page MenuHome GnuPG
Create Task
Maniphest T7949

Kleopatra: Initial language not selected according to windows settings
Open, Needs TriagePublic
Actions

Description

The initial language in kleopatra is not selected according to windows settings, e.g.

  • Settings
    • Windows display language: English
    • Country or region: Germany
    • Regional format: German
  • Result
    • In the Kleopatra language dialog
      • German is initially selected and clicking OK does not generate a klanguageoverridesrc file, so German can't be selected without selecting another language first
      • Selecting German after the klanguageoverridesrc was generated will display both Kleopatra and Gnupg System Tab in German (ok)

Notes:

  • The language switch is about to be removed in a future version and a fix would be obsolete then
  • If removal means just deactivation and users are able to reactivate it, a fix might still make sense
  • Being able to easily switch the language might also be reqired for testing purposes:
    • Otherwise one would have to download all Windows languages, which takes both time (language download was really slow for me) and disk space
    • Changing the language would require to log out/in, applies to the whole OS and navigation would be hard, if one cannot understand the language

Details

Version
gpg4win-5.0.0-beta413 @ win11

Related Objects

Event Timeline

timegrid created this task.Mon, Nov 24, 11:10 AM
timegrid created this object with edit policy "Contributor (Project)".
timegrid mentioned this in T7874: Kleopatra: GnuPG System configuration not translated.
timegrid added a comment.Mon, Nov 24, 11:13 AM

Regarding the tests: Being able to set the language for Kleopatra via some environment variable would be fine, too.

• ikloecker added a comment.Mon, Nov 24, 11:22 AM
In T7949#208870, @timegrid wrote:

Regarding the tests: Being able to set the language for Kleopatra via some environment variable would be fine, too.

But then you wouldn't test the real code which makes the test not very useful. In any case, setting LANGUAGE should already work. gpg CLI lacks support for LANGUAGE on Windows, but there's LC_ALL and LC_MESSAGES and LANG which work for gpg CLI on Windows. I'm not sure how those latter variables work with Qt and/or the standard gettext used by KF on Windows.

timegrid added a comment.Mon, Nov 24, 12:02 PM

I'd prefer the language switch for testing, but I mostly had tests for translation issues in mind, e.g. wrong translation language, tooltip size in some language - which probably should be covered by setting the language via the envvar. I'll do some tests to see, if this would work.

Another note: If the language switch is removed, there's also no way to specify the fallback language, i guess? Not sure, if this is a problem.

• ikloecker added a comment.Mon, Nov 24, 1:04 PM

I think Gpg4win will keep the language switch because for Gpg4win we don't disable any actions via action restrictions (as far as I know).

The translations that we support officially should be complete so that a fallback language (other than English (US)) shouldn't be needed. In any case, the fallback language only works for KF (and I'm not sure if it really works for all parts of KF), but not for GnuPG. And, if anything, then we'd have to support the Windows language preferences (which Qt supports by using newer Windows API, but not if built with MinGW).