Looks good to me on gpg4win-5.1.0-beta658 @ win11:

Looks good to me on gpg4win-5.1.0-beta658 @ win11:

Patch up in https://invent.kde.org/graphics/okular/-/merge_requests/1414 that removes the finish ('cause it will not work) when reloading

Looks good to me on gpg4win-5.1.0-beta658 @ win11.

Looks beautiful to me on gpg4win-5.1.0-beta658 @ win11

Issue Found

• Details
  • Table size is still 3 rows for OpenPGP certificates (fix only works for S/MIME)
    
    

Looks good to me on gpg4win-5.1.0-beta658 @ win11:

Public key will not happen. It might also get removed from NSS backend.

This happens only, if the Kleopatra main window is open and behind Okular.

If this is only a visual cutoff/fadeout, and the content still is still displayed, after the width was adjusted.

Ah, well, the window with can obviously be changed, so a cutoff/fadeout would be fine.

A cutoff/fadeout could be problematic, if you have multiple certificates you have to distinguish.
There is some information available in the tooltip, but it might be missing some (no email in this example):

I guess cutting it off / fading it out is the only sane way of dealing with infinite long uid's ?

I think this need to be handled by Kleo ? @ikloecker

In T8018#220049, @svuorela wrote:

whattabout https://invent.kde.org/graphics/okular/-/merge_requests/1404 ?

In T6632#220019, @timegrid wrote:

Note: the "qualified" tag overlaps long uids (I'll create another ticket for that):

Note: The Kleopatra window is often opened behind the other windows, and you think it does not work, so you click again and another hidden window opens. It would be nice, If this could be fixed (will create another issue for it)

In T8018#219988, @ebo wrote:

seems to me, that the details here are no details and could be dropped completely. I'm i overlooking something?
And wouldn't "Could not sign: Wrong passphrase" be better? Or even better: "Signature failed: Wrong passphrase"?
In Kleopatra we have: "Signing failed: %1"

it will be Sune_Vuorela_FPR_public.asc hopefully soon. and hopefully ascii armored.
I don't have the key-id handy, only the full fingerprint, and I'm not sure we should be playing scrabble with the keyId in Okular code. I'll see if I at some point can get the keyid thru.

Seems I am behind the times ;-)

In T8293#220072, @ebo wrote:

Well, Kleopatra keeps the whitespaces in names. If you handle them differently it will again deviate from what Kleo does.

Well, Kleopatra keeps the whitespace in the name.

underscores usual I'd say. There is no semantic in the format of the file name.

3 rows: https://invent.kde.org/graphics/okular/-/merge_requests/1405
most other things: https://invent.kde.org/graphics/okular/-/merge_requests/1406

name contains spaces. How to mangle those ?

Yes, that one:

• Fingerprint: 98111E67AE06F2BEFD2BDE10C5D6C919005F36A4
• Keyid: C5D6C919005F36A4

Looks good to me on gpg4win-5.1.0-beta653 @ win11

In T8018#220049, @svuorela wrote:

whattabout https://invent.kde.org/graphics/okular/-/merge_requests/1404 ?

by KEYID, do you mean the short keyid? Okular doesn't actually know about that and there is no easy way to get there.

In T8293#220040, @ebo wrote:

if at least the content of the export is the same

After thinking about this, how would we deal with translations ? Currently signed is marked for translations and trying to autodetect adding more signatures is likely problematic: foo_signed_signiert_signeret_...

whattabout https://invent.kde.org/graphics/okular/-/merge_requests/1404 ?

Looks good to me on gpg4win-5.1.0-beta653 @ win11:

yes, the folder is OK.

Issues found:

• Name is <FPR>_public.asc now, not <NAME>_0x<KEYID>_public.asc
  
• The suggested folder is now the folder of the opened file, which is definitely better than the windows system dir. @ebo are you fine with that?

Looks good to me on gpg4win-5.1.0-beta653 @ win11:

Issues found:

• General
  • "Name" is still "Common Name (CN)"
    
• Details
  • Fixed table size with 3 lines is a bit small, better use at least 6 lines or better scale with dialog window height
  • Issuer still shown
    
  • "Userid" is still "Subject", Textarea is not filled on selection
    
  • "Public Key": Textarea also not filled on selection
    

Note: the "qualified" tag overlaps long uids (I'll create another ticket for that):

Looks good to me on gpg4win-5.1.0-beta653 @ win11:

In T8018#219988, @ebo wrote:

seems to me, that the details here are no details and could be dropped completely. I'm i overlooking something?
And wouldn't "Could not sign: Wrong passphrase" be better? Or even better: "Signature failed: Wrong passphrase"?
In Kleopatra we have: "Signing failed: %1"

In T8018#219988, @ebo wrote:

seems to me, that the details here are no details and could be dropped completely.

seems to me, that the details here are no details and could be dropped completely. I'm i overlooking something?
And wouldn_"Could not sign: Wrong passphrase" be better?

Upstream fix in https://invent.kde.org/graphics/okular/-/merge_requests/1403 - let's get it merged and redo our tarball.

Looks not pretty, but good to me on gpg4win-5.1.0-beta653 @ win11:

*Still open*

• This needs to be tested on vsd-3.3.7 @ win. If the behavior is the same, this might need to be backported.

Looks good to me on gpg4win-5.1.0-beta653 @ win11:

Looks good to me on gpg4win-5.1.0-beta653 @ win11:

https://invent.kde.org/graphics/okular/-/merge_requests/1228

https://invent.kde.org/graphics/okular/-/merge_requests/1393