The high-contrast modes disable all colors, but for normal dark modes we might have a problem with some of the predefined colors.

Regarding font selection: Remove it. It's sufficient that people can set colors, italic, bold, etc.

From the support angle, the worst of these issues is that the default will not be restored for VS-NfD. But then: nobody has inquired about that yet…

We might also consider going all out and allowing a configurable appearance on a per certificate level. Then this feature would see an increase in use for sure. But it should work without issues, in that case, as then people will notice them…

In T7212#188683, @ebo wrote:

We might also consider going all out and allowing a configurable appearance on a per certificate level. Then this feature would see an increase in use for sure. But it should work without issues, in that case, as then people will notice them…

Uhm, you have to explain that one to me. I have no idea what the use case for that would be, so I would not consider that. And as you think that this would drastically improve the feature I am curious why you think that.

You could use colors, fonts, icons to mark any certificate you want instead of having to use tags and filter by them. You could even put their company logo on certificates of your communication partners.

Another thing, unrelated to my flight of fancy above:
We should mark TrustedKeys in the certificate list. But I guess setting colors by Kleopatra filters is completely different from setting them via registry keys. So I would make another ticket for that.

Although this could maybe be another argument for setting up the whole certificate appearance stuff differently

I vote for removing the UI for configuring the appearance of the certificate categories completely from Kleopatra. This would solve all usability problems in an instant. People who want to go crazy with colors can edit the rc file.

Hard to decide as we have no data how much it is used. :-/ But I tend to agree here. We should not loose sight of the fact that Kleopatra should be more of a diagnostic tool and provide all the information a user might need to solve their issues with signing, verification, encryption and decryption. Kleopatra is not something a user uses so often that they play around with appearance or so like they maybe would in a MUA. Certificate management is just an unwelcome side effect required for crypto. But users do not want to do certificate management for its own sake.

But there may be exceptions. And such users, who really like to explore every nook and cranny of Kleopatra might be the "champion users" in an Organization who always speak out in favor of it.

Mh, no, on the other hand the style is useful in the "All certificates view" to make distinctions based on multiple parameters. "Like trusted S/MIME root certificate" and it is useful to see that right away instead of using the filters. So my vote would be to clean it up, but keep it in general.

Just to clarify: I didn't say that we should remove the coloring/font style of certificates. I just said that I vote for removing the UI for changing the colors and font style.

User: "The purple certificate doesn't work." Support: "Purple? There are no purple certificates." User: "Yes, there are. And pink ones and bordeaux and mauve." ;-) Support people love users customizing their apps because it makes customer support so much more fun.

I'd be in favor of keeping the UI and just fixing the most significant bugs it has.

https://invent.kde.org/pim/kleopatra/-/merge_requests/255 fixes some low-hanging bugs to make the configuration behave more as expected

in 5.0-Beta-190

• the "Defaults" button seems to reset to the original appearance after first installation (instead of removing all defined appearance settings) -> OK
• the filter order shown is different than before -> probably ok
• I do not see how removing an icon is possible (as suggested by the commit above) -> not fixed

Why are there 2 buttons for (probably) the same thing: "Default Appearance" and "Defaults"?

(Edit 2025-06-13: changed the first line with "Default Appearance" to "Defaults", this was a mistake cause by me not using the EN version)

In T7212#201964, @ebo wrote:

Why are there 2 buttons for (probably) the same thing: "Default Appearance" and "Defaults"?

"Default Appearance" (like all other buttons on the right) only applies to the currently selected category. "Defaults" resets all categories.

Thanks! Maybe we should add a tooltip? "Default Appearance" does not have one and I do not find this self explanatory.

What is fixed, what needs still needs to be done and should go into another ticket?

From the support angle, the worst of these issues is that the default will not be restored for VS-NfD. But then: nobody has inquired about that yet…

The first support case regarding this came in today

Font selection dialog lets the user choose a font size, which is then not respected - can we disable selecting the font size?

@ikloecker: could we? But I consider this to be a minor thing.

Consider removing Italic, Bold, Strikeout check boxes, since those can also be selected through the font (or disable these in the font selection?)

I'd say leave it as it is. it does no harm. Would be different if there was a wish to add this, then I'd say it's not necessary.
Hm, might it be that those are the only properties one can change about the font? Additionally to the font itself.
But strike-trough does also not always work…

I'd say we use this ticket for the resetting of the default settings and make a new one with wishlist prio for the appearance config

@ikloecker I'd like it if we could backport the resetting of the preferences to vsd34.

I've checked this works with vsd4.0-Beta VS-Desktop-4.0.90.1203-Beta
Though I wonder why the local libkleopatrarc has this four settings after ressetting everything:

[Key Filter #15]
font-bold=true

[Key Filter #16]
font=Segoe UI,9,-1,5,400,0,0,0,0,0,0,0,0,0,0,1

[Key Filter #3]
font-bold=true

[Key Filter #5]
font-bold=true

What is filter 16?

Filter 16 is the new filter for valid certificates. The problem could be that the version you tested did not yet have this filter.

That font-bold=true is saved after resetting might be a bug in the check whether the setting matches the default for this filter.

added vsd34 for the resetting of the defaults part only

The remaining open points of this ticket will be "won't fix" for now. When we plan to change something here, we should open new tickets, this one got confusing.

One observation as note to self: The font changes seem to behave differently on Linux and Windows, e.g. strikethrough apparently works on Linux, but not on Windows 11 (I didn't check 10).

For the tests on vsd34: we ignore the 4 settings as shown above in the remaining local config. They do no harm as they are the same as in the default.
When one of these defaults changes - like here - people will have to reset to defaults here to get the new defaults, iff they already had a local libkleopatrarc.

Backported for VSD 3.4

Seems I forgot to note that icon removal works when resetting to defaults. And the VSD related Categories are no longer shown in Gpg4win. Tested now with Gpg4win 5.0.2, but I believe it was already ok in 5.0.0.

Not yet checked: If the VSD related Categories are shown in a VSD-Beta based on the 2.5 branch.