Works, tested with VS-Desktop-3.2.94.474-Beta

The layout is totally different now in VS-Desktop-3.2.94.474-Beta but the "generate new key" action is now hidden for the slots (while still there in Gpg4win 4.4).

There's the VERSION file that is used for customizing the About data for VSD and GnuPG Desktop. It's an ini format file that's read with QSettings.

Doing the changes to the text is easy enough, but I'm not sure whether we have a nice way of doing something only in a VSD version.

The changes hat to be reverted, a working solution is planned for later

Looks like there's something not correct in the completion model. Or we use different criteria for showing the blue "i" (as "information") which doesn't make it better. Reopen?

This is long done, but only for Qt 6-based releases. Andre's comment T6663#175481 has also been addressed.

Tested Gpg4win 4.4:
Interesting, when you search for the UID, it looks as before, with the green check mark:

I think this is resolved. In the Sign/Encrypt dialog we now offer the individual user IDs instead of the certificates, i.e. the two user IDs of the Udo certificate are both offered and one should be listed as certified and the other one as not certified (if one is certified and the other one isn't; for me both user IDs are ultimately trusted).

I suggest to make the following text changes for the VSD versions only:

This might fix the issue https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=commit;h=cf13e915581ca32e05e229cc54ef8e35753128e0

Gpg4win-Beta-75:
Checked the property details of some files in "Progams (X86)" and found several without product name, E.g. libgpg-error-0.dll and other dlls located at C:\Program Files (x86)\GnuPG\bin.
Or gpgolconfig.exe at C:\Program Files (x86)\Gpg4win\bin and the examble from above, libKF5JobWidgets.dll, shows no product name either.

This is now merged into master

After recompiling, it works!

I backported the work of Andre for qt6 to master/kf5. It's in the branch work/carl/product-name-kf5

This is also relevant for VSD 3.3. Backport is not needed, but gpg4win/VSD needs to include current gpgme.

gpg4win-Beta-50:
Columns are now displayed as expected with a fresh installation, too.

That was resolved with vsd 3.2.0

Without administrator rights it does not work for me, since it then cannot write to %PROGRAMDATA% to install the VS-NfD mode config files. But the only thing for "does not work anyway" that I know and could quickly see is that "IPC connect call failed" problem with GPGEX (which we are planning to remove / replace anyway). So I don't think it is very important to remove this and addtionally we do not know if this is something that is used, we have offered it from the beginning but have no data if our customers use it. We can suspect that we would have seen more support questions about the gpgex error if it was widely used. But I always thought that the "only for me" installation option was useful for some use cases.

I think the executables also use the same values for translation.

Okay, I see now that this is US-English and Unicode.

Okay. let me do that for the next library releases.

The additional changes have been backported for VSD 3.3

To clarify what I mean by the missing VarFileInfo block. Currently the GnuPG binaries have versioninfo.rc files but only the version number is displayed for dlls as their pattern did not have the VerFileInfo block: The libassuan-0.dll displayed in this screenshot is from the 2.2.43 package and the assuan-9.dll is self compiled but including the patch below that. I would like to commit such a patch to all libraries that require it if that is okay with you.

I added some comments to the commit. But

A better solution might be to use categories to have that element "this message will be signed / this message will be encrypted" above the edit window. But what I find more important and so much more a high priority is that in cases we have a failure saving the draft info flags an error message should come up. This happened for a customer and in the logs I could see that MAPI returned an error. the button was not toggled in this case but the mail also was not marked for encryption. T7144 is the task for that so I'd suggest to start with that one.

In gpgoladdin:

Changing the icon is unusual and does not match a native look and feel in Outlook where toggle icons are there for a reason, to be toggled or not. This is also the way how Outlooks native encrypt & sign works and Microsoft will probably have thought about this a bit.

Phew. Got it. a new script: "gccwrap.sh.in"