@werner said the reading order should be like on the page https://gnupg.com/vsd/kleopatra-settings.html:

Tested with Gpg4win 5.0.2 (Beta):
Registry settings SOFTWARE\Gpg4win\Kleopatra\<config group>\<config entry>
works (I used [CertificateCreationWizard] EMAIL_placeholder for testing)

Ok in Gpg4win 5.0.2. (Beta), in German:

config file: Sorry, I got confused, it has to be %APPDATA%\GnuPG VS-Desktop\kleopatrarc in this case (VS-Desktop-4.0.90.1203-Beta), of course. And this one works.
Registry entry SOFTWARE\GnuPG VS-Desktop\Kleopatra\CMS\SaveCSRAsPEM does not work, though. But this is a separate issue, seems all Registry entries do not work in that build.

Works with VS-Desktop-4.0.90.1203-Beta when putting this in C:\Program Files\GnuPG VS-Desktop\share\kleopatrarc
CSR is then saved as .pem file with ascii-armored content.

The new German tool tip is shown in Gpg4win 5.0.2 (Beta)

Thanks for the info!

Does not work in the latest Gpg4win builds (5.0.0. to 5.0.2).
I have no idea which commit would be needed, I see no commit with this bug-ID.

So ok, go ahead Ingo with your plan in https://dev.gnupg.org/T7502#213972

As the migration to keyboxd will happen not too far in the future, we'll close this ticket.
Keylisting should meanwhile already be faster due to other changes.

I was too fast with closing this, seems it is reproducible under special conditions. But not by me, here it works.

Me neither, neither on Win10 or 11. I tried the original description and https://dev.gnupg.org/T7943#208784

This is nothing we want to do in Kleopatra. The "Force" button will be removed shortly even for MDC error.

Please add the hint you mentioned.

The fix is only a workaround, the duplicate entries are no longer shown in Kleopatra, they still exist and multiply on save.

How about "Certification includes that you check the fingerprint against a trusted source."? "Means" seems wrong to me. @hej, please comment

ok, lets do this. I'll update the description

How about changing the text after sentence two simply to:

Do we agree to drop bolt font for QES certificates?
Will we change this for VSD 3.4?

This ticket is now obsolete, as we will force the setting of autoencryptUntrusted=0 via the registry in Ticket T8090

Maybe we could show instead the text "No keyserver is configured."? Need not be in the same place. This would also be helpful in the other case, where you go to the search via "Lookup on Server".

Forget my comment above. Or consider it as the "before" part of the task description…

Fixed for KF6 versions.

Meanwhile all executables are signed.