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

I would say this could be treated as a duplicate or subtask of T7147: Kleopatra: Add debug information / Log handling KWatchGnuPG is in my opinion not very useful, since as a developer debugging things the command line and "watchgnupg" without the K are more then enough, KWatchGnuPG is basically just a qprocess output viewer of watchgnupg. IMO it would be similar if we would just execute CMD or Konsole with "watchgnupg" and show that window. Logging to a socket has the advantage that the entries are displayed in the order they come in while with files there is an issue of io synchronization and not all components can log in the same file. But you could use same QProcess / watchgnupg to "sync" the log entires and then write them to a file.

works in VS-Desktop-3.2.93.33-Beta

I wouldn't hide the table. We don't hide any tables (e.g. also in smart card view) if they are empty. I would resize ones on very first show (if restoreColumnLayout() returns false). This fixes the initially cut column titles. And then I'd resize to content when the search results are shown, but also only the very first time (i.e. we'd need to remember the first show).

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

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

Thanks.

afaik "Valid Until" is actually available for keys coming from WKD

• The status column is already removed in the gpg4win branch but not yet in the test version
• afaik "Valid Until" is actually available for keys coming from WKD
• For the column widths, we could hide the table until the initial search results come in and then resize to content, or just always resize to content when results come in

The whole problem that we now had to take care of marking mails as Read was a misunderstanding of the code. As I assumed since we saved the mail. The property change of "UnRead" would then not be synced to the server, but more testing and user feedback after the last release has shown that the even FC99 which we observed in the "Uncancellable write event" cases was sent to us in conjunction with the property change of UnRead.

Very good suggestion! +1
I believe Werner and Alexander will agree, too, as we talked about that tab the other day and that showing only the last certification would be preferable

I would propose two more changes to make the dialog behave in a way that seems logical to me:

I like KMessageWidget although I think it's not very accessible, i.e. the user isn't notified when it's shown. Hmm, we could probably focus the message widget when it's shown. Then screen readers should read the text.

I'm not sure this is a good idea. We are trading one UI quirk (all columns except the first one can be moved) with another UI quirk (sometimes all columns can be move and sometimes all columns except the first one can be moved). The first behavior is at least consistent across all views.

https://invent.kde.org/pim/kleopatra/-/merge_requests/273 and https://invent.kde.org/pim/libkleo/-/merge_requests/127