After further discussion, I propose the following. All tool tips and the last dialog text were changed:

Edit 2025-06-26:
And please Fix the ALT shortcut in the "Sign / Encrypt", "Sign" and "Encrypt" button to S or E, respectively. One can hardly see the mark at the "i" and its unintuitive, anyway:

In T7379#195089, @ikloecker wrote:

Kleopatra does now read the certificates from the card and import them itself instead of relying on gpgsm --learn-card.

since nothing was changed, that's a wontfix…

Remove the lines starting with ShowResultsAfter[...] in kleopatrarc

That works using a gpgconf.ctl file side by side to gpgconf{,.exe}

I'm not working on this anymore. Kleopatra should be prepared for using VSD, GPD, and Gpg4win in parallel (provided they use different homedirs). What's left is the actual parallel installation which might be solved in part by using NSIS for Gpg4win and MSI for VSD/GPD. I'm not sure how the parallel installation of different versions of gnupg is solved, but I guess Werner has that covered.

For KF5-based builds this is resolved because the improved heuristic for detecting light high-contrast themes (like "Desert") is used for VSD 3.3 and Gpg4win 4.4.

For simplicity (and because I think entering tab characters isn't really essential for the notepad) I decided to go with the first solution.

Ready for testing.

and for certification revocation (and some other places): https://invent.kde.org/pim/libkleo/-/merge_requests/197

For card stuff: https://invent.kde.org/pim/kleopatra/-/merge_requests/400

For the tooltips: https://invent.kde.org/pim/libkleo/-/merge_requests/196

This seems to be a good opportunity to replace paperkey with a new tool to take advantage of the smaller ECC keys which allow us to re-generate most stuff.

Ok, it was a missing update (although windows claimed to be up-to-date).
After installing 2025-06 [...] KB5060829 the Microsoft Print to PDF feature is available again and printing also works in Kleopatra/Okular.

A second patch fixes the problem with the button in the smart card view.

I have added a patch to disable recoloring of the status icons in Gpg4win. This ensures that the status icons in the selected rows don't get all-white.

Upstream bug report for invisible status icons: https://bugs.kde.org/show_bug.cgi?id=506434 (Icon coloring is inherently incompatible with colored Breeze status icons)

It's also the same error in Okular, when a pdf is printed.

Same on gpg4win-4.4.1 @ win11 (here a bit more debugview context)

3	3.503991	8584	kleopatra.exe	org.kde.pim.kleopatra: Paperkey export finished:  0 status:  QProcess::NormalExit
4	3.691599	8584	kleopatra.exe	QPrintDialog: Cannot be used on non-native printers
5	3.691981	8584	kleopatra.exe	QPrintDialog: Cannot be used on non-native printers
6	3.692752	8584	kleopatra.exe	org.kde.pim.kleopatra: Printing aborted.

Works fine here.

version

C:\Users\g10\Desktop\tmp\scdecrypt>gpg --version
gpg (GnuPG) 2.5.8
libgcrypt 1.11.1
Copyright (C) 2025 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

gpg --version?
gpg -K?

You're right, it also errors on gpg directly:

I can't reproduce. Please check whether this works if you use gpg directly; it's a bit unlikely that this is kleopatra-specific, since kleopatra doesn't really care whether the key is on a smartcard or not.

a: expired certificate

In T7639#202620, @timegrid wrote:

If this should also work in gpg4win-5.0.0-beta336 @ win10 (beta compliance mode), it does not:

In T7610#202487, @timegrid wrote:

• compliance note in sign/encrypt next to sign/encrypt button (both for file and clipboard) unreadable in black/nr1/nr2 and also in dark mode:

If this should also work in gpg4win-5.0.0-beta336 @ win10 (beta compliance mode), it does not:

This only happens, if the smartcard key

• is the only key in the keyring or
• was used for sign/encrypt earlier and thus saved as selection default.

Not sure, what to expect, but generally looks fine for me in gpg4win-5.0.0-beta336 @ win10:

In T7610#202487, @timegrid wrote:

• compliance note in sign/encrypt next to sign/encrypt button (both for file and clipboard) unreadable in black/nr1/nr2 and also in dark mode:

I guess, that's ok then, moving this to done.

Thanks, confirmed then, moving to Done.

In T7594#202471, @timegrid wrote:

Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).

Issue with pretty kyber names moved into: T7708.
Moving this to done.

General issues with unformatted fingerprints/keyids moved into T7707.

In T7232#202509, @timegrid wrote:

With above configuration it seems to work on gpg4win-5.0.0-beta336 @ win10.
Any way to verify in kleopatra, that the setting was applied?

In T7394#202514, @timegrid wrote:

• Kyber algorithms display only their ecc part

I guess that the missing formatting of fingerprint or key ID isn't restricted to v5 keys. -> separate ticket

In T7345#202503, @timegrid wrote:

• Some/Most "Not VS-NfD compliant" notes do not have the (beta) suffix (probably fine?)

Looks good to me on gpg4win-5.0.0-beta336 @ win10:

• Full stops are fine now
• "not VS-NfD compliant" for invalid signatures not shown anymore (tested in vsd compliance mode)
  

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10:

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

With above configuration it seems to work on gpg4win-5.0.0-beta336 @ win10.
Any way to verify in kleopatra, that the setting was applied?

Tested on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

I tested the VSD elements on gpg4win-5.0.0-beta336 @ win10 (beta compliance mode).

Happens also in the group config (warning icon):

Looks good to me on gpg4win-5.0.0-beta336 @ win10.

One screenshot of the test setup for reference:

Mostly looks good to me on gpg4win-5.0.0-beta336 @ win10/win11.

since @ebo asked about this: the current state is that the first column of all tables can't be moved. This seems to be what we want, so nothing needs to be changed and nothing was done to change this. I guess this ticket can be closed.

Related? In smartcards view:

Shouldn't the enabled close button in win10 / disabled text / nr2 have green color? (it's the "search certs on server" dialog).