With my initial suggestions, modified by:

Another thing (should definitely go into a new ticket if we want to do something regarding this):

Again for Gpg4win 4.4.0, this time with better attention (and definitively encryption only):

Shorter version:

Possible explanation text for the user regarding the background of the question (probably to long):

This is the current (VSD 3.3.0) state for Japanese (with German as fallback):

Everything mentioned above was translated and is now shown that way in all three languages.

I would keep the "create group", too.

In T7515#198012, @alexk wrote:

Regarding the suggest list I would change the following:
but keep:

• Enable/Disable Certificate

Regarding the suggest list I would change the following:

Fixed.

In T7515#197774, @TobiasFella wrote:

I'd suggest removing:

I'd suggest removing:

If a single OpenPGP certificate is updated then we now show the same detailed information for the update from WKD as for the update from a keyserver, i.e. if the certificate didn't change via WKD then we say so.

I think there's some confusion.

changed the workboard to gpd5x as this is still the case in Gpg4win 5.0-Beta versions.

Gpg4win-5.0.0-beta32
Works!

Gpg4win-5.0.0-beta32:
The remaining attempts are listed:

You need to be asked this question when you restore the backup of all of your keys or when you migrate all your secret keys to a new computer.

The situation seems to be even more complicated: If I click "yes" or "no" in this dialog, I *do* get asked for all certificates that are being imported. If I click "Cancel", no more dialogs show up.

Tested locally:

• Build the Docker image for building the AppImage (using the archived CentOS 7 packages).
• Build an AppImage for Gpg4win 4.4 with the unsplit gpgme repo.
• Build an AppImage for Gpg4win 4.4 with the split gpgme repos (T7262).

I'm not sure what Kleopatra should do differently. Kleopatra relies on the error messages provided by gpgme which in turn relies on gpg's status messages.

For Gpg4win 4.4.0:
Encryption: ~2:35
Decryption: ~0:44

To make the test complete for VSD, here the times for decryption (and verification) of the 3G file from above:

• VSD 3.2.4: ~3:36
• VSD 3.3.0: ~2:20
• command line: ~2:30 (maybe the bit slower than in Kleo is because this was done in a shared folder of the host system instead of on the c: partition)

The cli was done in both tests with the gpg version from VSD 3.3.0

FWIW, If a fix is really required for gnupg this will be done for gnupg26 and not for gnupg22. However, it is mostly a kleopatra issue.

Tested encryption (+ signature) via Kleopatra with a 3 GB file (random data) with:

• VSD 3.2.4: ~ 5:20
• VSD 3.3.0: ~ 4:25
• command line; ~4:25

Ok, then this will not be included in the VSD versions until we switch away from gpg 2.2

21f7ad563d9b was not backported to gnupg 2.2, so this can't be done yet

It's missing a check for the required gpg-2.2 version. I will add that

Closing as there are now 2 follow up tickets for the open issues I found.

VS-Desktop-3.3.0.0 now has the translation. Will be in Gpg4win in the next release.

In contrast to Gpg4win 4.4 in VSD 3.3.0 dragging a plain file onto Kleopatra will return an error. Decryption and importing certificates works, though.

Works as well for VS-Desktop-3.2.94.481-Beta

In VS-Desktop-3.2.94.481-Beta the feature is not available in the context menu in Kleopatra.
So in VSD 3.3.0 this will be missing. What works is disable/enable on the command line and Kleopatra will then not list a disabled certificate with most filters.

VS-Desktop-3.2.94.481-Beta: OK