Revoking a user ID specified by the actual user ID may fail because of
charset issues. Specifying the user ID to revoke by its hash makes this
more robust. This is supported since GnuPG 2.3.7.

GnuPG-bug-id: 4087

This prevents a "no key" error from being displayed briefly while a key
lookup is running in the background. The error will be shown if the
lookup wasn't successful or if no lookup was started in the first place.

GnuPG-bug-id: 5945

With this change the summary line of the current key/group is always
updated when the key/group is updated while the user is not editing the
entry.

GnuPG-bug-id: 5945

This reduces the time the error is shown because the certificate line edit
does not need to wait for a complete refresh of the key cache (which
happens automatically in the background) to show the retrieved key.

GnuPG-bug-id: 5945

Instead of showing the question icon for ambiguous entries and the
error icon for entries not matching anything, we show the question icon
as long as the user enters a recipient and we show the error icon (and
the error message) once the users commit their entry (with Return or Tab).

GnuPG-bug-id: 5945

Those helpers are not specific for revoking user IDs.

GnuPG-bug-id: 4087

A new Gpg4win release is around the corner.

The wrong brace caused an incomplete translation and
also that the first string was always taken.

If the keys were reloaded by the key cache, then we may have to (re)load
the key details because the key cache usually doesn't load all details.
This caused problems when checking whether the user right-clicked the
last valid user ID because sometimes no signatures were available.

GnuPG-bug-id: 4087

After an operation which changed the key update the key with the
dedicated Key::update() and then call setUpdatedKey(). Calling
setKey() would trigger a possibly expensive remote update which shouldn't
be necessary after local changes.

GnuPG-bug-id: 4087

GnuPG-bug-id: 4087

gpg does not allow revoking the last "valid" user ID where "valid" means
that the user ID is neither revoked (the user ID, not the key!) nor
expired (again: the user ID, not the key!).

GnuPG-bug-id: 4087

GnuPG-bug-id: 4087

This prevents multiple context menus from being opened when right-clicking
on the user id of an OpenPGP key.

GnuPG-bug-id: 4087

The result label now holds HTML text and not just the user ID anymore.

GnuPG-bug-id: 5916

Add settings ValidityPeriodInDaysMin and ValidityPeriodInDaysMax to
restrict the allowed values for the validity period of new OpenPGP keys.

GnuPG-bug-id: 5864

"accessort" doesn't occur anywhere in kleopatra

Separate the update of the enabled state of the widgets and the checked
state of the widgets. Update the enabled state only if the key type is
not forced, but always update the checked state.

This fixes the selection of the correct usage flags if the key type is
forced.

GnuPG-bug-id: 5865

* First, update visibility of key type and usage widgets
* Then, update enabled state of key type and usage widgets depending
  on key protocol and immutability of key type
* Finally, update the checked states that depend on the key protocol

GnuPG-bug-id: 5865

GnuPG-bug-id: 5916

GnuPG-bug-id: 5916

This way the same error messages are used for the error summary as for
the individual input fields.

GnuPG-bug-id: 5916

This allows us to omit the prefix if it's not wanted.

GnuPG-bug-id: 5916

GnuPG-bug-id: 5916

Setting the input widget as buddy of the labels ensures that the labels
are not considered as unrelated labels by assistive tools. This prevents
at least orca from reading the hint text as part of the dialog text.

GnuPG-bug-id: 5916

Set the accessible variant of the hint text as accessible name of the
hint label, so that assistive tools "reading" the hint label use the
accessible hint text.

GnuPG-bug-id: 5916

This allows to set alternative error messages for use by assistive tools
if the displayed error messages are not suitable.

Moreover, the error messages are made more specific and are worded as
instructions if appropriate.

GnuPG-bug-id: 5916

This makes the API more similar to setHint().

GnuPG-bug-id: 5916

This replaces the less accessible tool tip with a hint text that is shown
between label and input field.

GnuPG-bug-id: 5916

GnuPG-bug-id: 5916

Use a bold font to make the labels more prominent.

GnuPG-bug-id: 5916

Putting the labels above the input fields makes the dialog also work with
large magnification. Additionally, we put the error label above the
input field (but below the label).

GnuPG-bug-id: 5916

To indicate required input fields the text " (required)" is appended
to the label. We do not add "required" to the accessible name anymore.
In the Add User ID dialog we remove the colon at the end of the labels
texts and we do not need to set an alternative accessible name anymore.

GnuPG-bug-id: 5916

GnuPG-bug-id: 5916

This is a workaround for missing focus indicators for labels in many
Qt styles. To ensure that users see that a label has keyboard focus
we select its text.

GnuPG-bug-id: 5916

If assistive tools are active, then certain labels need to be focusable,
to make the text of those labels accessible. The LabelHelper takes care
of setting the appropriate focus policy for the associated labels.

GnuPG-bug-id: 5916

Some screenreaders read the ":" if the field is required or if the
input is not valid. Setting an accessible name without the trailing
colon avoids this.

GnuPG-bug-id: 5916

If the name or the email address is specified as required via the
configuration, then set the corresponding input fields as required.

GnuPG-bug-id: 5916

This adds functionality to require a text input field to be filled out.
If input is required, then this will be indicated to assistive tools.
A special error message, that is displayed, if a required field lacks
input, can be set. hasValue() can be used to check if a value has been
entered.

GnuPG-bug-id: 5916