ok, I like your proposal. To recap:

I'm not sure if we are talking about the Encrypt-to-self drop-down or the Encrypt for others input fields. On the other hand, I see little reason to treat both differently.

ok, new try. As Ingo now clarified that that "nothing was imported" and "nothing was considered" is synonymous for him, then I misunderstood that comment. As far as I understand the "considered" that would mean that a tab would come up for import of unchanged keys, too.

ok, to make it clear how exactly to implement and test this, let me rephrase what my interpretation of your comment is:

Turns out

• the singular instead of plural in the German version is a translation thing and should now be fixed (but is not in the testversion beta35)
• there is another issue muddying the waters regarding search in WKD, for which I will create another ticket

I have to correct myself. After restarting Kleopatra, only the following columns are shown, without any changes from my side:

Well, i can live with it. It would be an improvement.
I would prefer if no import tab was created if a key has not been updated and therefore nothing was actually imported. But I see that this would be more complicated to implement and I have no strong opinion on this anyway.

On a fresh install Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta35) are now all available columns displayed by default:

Tested with version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta25)

In Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta25) the button is not shown any more.
As it was already not shown in VSD 3.2.2, closing this for all workboards

Then I would propose to add additional text at the top of the tool tip for VSD versions only. Something along the lines of: "Please check with the approval document whether this function is compliant for your smart card model."
Would that be possible?

What makes a card compliant? is it just about supporting algorithms that are compliant?

A minimal fix would be:

In reply to Ingo:
Ok, I can live with that but I still would like this message to be improved.
Looking at it some more I noticed some other details which bother me:

sorry, imprecise phrasing … we want this to be used in practice, which includes making the creation of a combined signature file easier.

After discussion we concluded that showing all signatures in one detached signature file is something we want soon.

After talking with Werner, I edited T7155 to include displaying the protocol column, too, because this is useful in combination with his wishes regarding the origin keyword which are:

Looking only at the text used, you get exactly the same messages used for single certificate updates, "The certificate has been updated" or "The certificate was not found.", both in the singular.

And "But "Update certificate" does still not query WKD (not even after restarting Kleopatra.)" seems to happen because the setting "Query certificate directories of providers for all user IDs" wasn't enabled.

Tested with Gpg4win-4.3.2-beta25:

Ok, follow up for the column is T7155.

Tested with Gpg4win-4.3.2-beta25:

For Gpg4win-4.3.2-beta25: Compendium is now listed before "More documentation".

I'd say "PIN counters:" is enough in combination with a tool tip. An additional documentation in a manual is always nice, of course. But do we really need the "PIN" here? As long as after the colon PIN, PUK, etc is listed, I think we could drop it here and say "Retry counters"
One could also contemplate using something like "No. of tries left".

Should I make a new ticket for making the origin column default for the search?

This depends on what this ticket was intended to cover.
I always see the tags in the main certificate view in VSD 2.2 as well as the current Gpg4win-4.3.2-beta25.

Tested with Gpg4win-4.3.2-beta25

Noticed when looking at the MR that there seems to be no error handling for the case that no ADSK is configured (or something is wrong with the configuration). At least I did not see any strings informing the user about an error.

Tested with 2025-05_gpg4win_Beta_23:

• "no certificates found" message shows as expected
• "Searching for matching certificates ..." is shown while searching
• Aborting search in the progress window works

Tested with Gpg4win-4.3.2-beta23: This works if I select the origin column for display. At least for WKD and keyserver.

Tested with Gpg4win-4.3.2-beta23:

Tested in Qt 5 build Gpg4win-4.3.2-beta23: Configuration dialog looks good.
Qt6 was tested by the developers

While I was about it, I also moved the compendium entry above the "More Documentation" entry.

works, tested with Gpg4win-4.3.2-beta23

works, tested with Gpg4win-4.3.2-beta23