The remaining issue "Wrong language in GnuPG error messages" is now also fixed. Until there's a new version of libgpg-error I've added the changes as patches.

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).

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.

In T7949#208870, @timegrid wrote:

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

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

Separate ticket for the "initial language selection": https://dev.gnupg.org/T7949

Please create a separate ticket for "The initial language in kleopatra is not selected according to windows settings". This is a bug in KDE Frameworks that's orthogonal to the issues of this ticket.

Looks good to me on gpg4win-5.0.0-beta413 @ win11

Tested on gpg4win-5.0.0-beta413 @ win11

Fixed. Kleopatra and the GnuPG System configuration and error messages coming from GnuPG should now always use the configured Windows display language regardless of the Preferred languages or the Regional format. (GnuPG on the command line will still use the Regional format.)

The language settings of Windows have strange influence on Kleopatra and GnuPG.

Right, gpg CLI output depends on it, too.

Notes to self:

• On Windows, libgpg-error's gettext replacement uses the value of LC_ALL, LC_MESSAGE, or LANG (in this order) if set. Otherwise, it uses Windows's GetThreadLocale. (gnupg should probably use the MUI API instead.)
• We should probably force Qt's/KDE's language on gnupg by setting LANG.

I have no idea how Qt/KDE and how gettext (resp. gnupg's replacement of gettext for Windows) react to Windows's "regional format" setting. It seems that Qt/KDE correctly use English despite German regional format while gnupg uses German.

The screenshots were made with

• ISO: EnglishInternational
• Windows Language: English (United Kingdom) - note: i installed English (United States), but can't select it
• Country or Region: German
• Regional Format: German

For such language tickets please give more information. What are your language settings? Not only in Kleo, the system language settings, too.

That's not surprising. The fix was made after GpgOL 2.6.7. And gpg4win-5.0.0-beta395 still seems to include GpgOL 2.6.6 only.

Looks good to me on gpg4win-5.0.0-beta395 @ win11

Issue is still present in gpg4win-5.0.0-beta395 @ win11:

This happens only in the 64-bit builds, i.e. with Gpg4win 5.

Thanks. Will go into 2.4.9 to be released soon.

All applied.

The umlauts are ok again!

I have reverted the commit mentioned by Carl and another text codec related commit for the Qt 5 builds. This will hopefully fix the broken umlauts in the progress messages.

This might be caused by https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win-tools.git;a=commit;h=30b5736a97d884452c9ad8c713600326ee06a7c3