I just want to remind you that we have added the possibility to explicitly disable opening of any URLs in Kleopatra. Don't introduce a new way to open a URL which cannot be disabled via the same setting.

Can you clarify on what the show parameter is intended to do? I don't yet see how it would be useful, as the distinction between VSD and gpg4win is already made by whether the respective file is present or not

In T7064#184630, @TobiasFella wrote:

Can you clarify on what the show parameter is intended to do? I don't yet see how it would be useful, as the distinction between VSD and gpg4win is already made by whether the respective file is present or not

For the FAQ link we do not want to ship a file but only use an online link but it should only be shown in VS-D mode. MMh thinking about this some more we also want to sow it in GnuPG Desktop (the not VS version) I am unsure yet how to detect this. Maybe with about data infos?

I think the DocAction idea doesn't really work well because it leads to empty submenus and bogus actions in the toolbar configuration and the keyboard shortcut configuration in builds that don't include the PDFs. And now, it seems, checking whether a file exists isn't enough anymore.

I think we need to rethink the way custom actions are added to the different gpg4win builds. Maybe the help menu actions should be created dynamically on runtime from information in some file that exists only in gpg4win instead of being created hard-coded and unconditionally as DocActions and then just hidden.

As there was some discussion in the ticket: what has been implemented? How can it be tested?

Help -> Additional Documentation -> GnuPG Commandline now brings up the GnuPG Manual in the browser for Gpg4win. This solves the issue that this menu entry (Additional Documentation) existed in Gpg4win and Kleopatra on general Linux but was empty. And the API does exist now to add more entries easily if suggested. I just checked on Linux in master and it worked for me.