This isn't needed with modern build environments, and can even conflict
with them.

gcc will complain, and we will fill out all fields later anyway.

These types caused an incorrect signed/unsigned behaviour, so let's make
sure we use the appropriate type.

gcc can get upset if they aren't in this order.

If we don't mark these as volatile then they might get reset on
longjmp() and the code will misbehave.

These are just values, so setting const on them has no effect as the
caller will get a copy.

These are all truisms because of the valid range of the types.

This allows us to separate accidental fall through from explicit ones,
which allows us to turn on such checks in the compiler.

If there isn't enough data, then the client reading the hash will fall
down and try to read the subtype instead, which isn't correct.

Invert the logic so we get a more consistent way through where we only
break out when there is insufficient data.

Do the same for the server code, for consistency.

These were not meant to fall through. Likely didn't have any adverse
effects, but let's fix it anyway.

This allows us to separate accidentally unused, from explicitly unused
parameters, which allows us to turn on such checks in the compiler.

No practical difference currently, but let's respect what this API was
supposed to do.

They have no need for it, so let's simplify things.

Everything in flags is already handled at a higher level.

The flags should always be empty anyway.

This makes sure the compiler doesn't complain about problems in those
files.

It's only the -Werror part we want to be conditional on being debug
builds.

This was not meant to be included in the previous commit. The static
storage for the font string is more than enough.

Fl::set_font() doesn't keep its own copy, so we need to make sure the
font string doesn't get freed or overwritten at a later point.

CentOS Stream isn't fully compatible with RHEL, and there are no useful
RHEL images available, so that leaves us with one of the new RHEL forks.

Add support for RSA-AES security types (Java version)

Use the font specified by the system for UI elements. For Windows and
macOS this is straight forward, but Linux is more complex as there is no
single source for this information.

Try to follow the actual padding that FLTK adds to these widgets.

The extra one pixel on each is because of a bug in FLTK's focus drawing
code, where the box is always one pixel too small in both dimensions.

This is how GNOME does things, so let's do the same so things look
similar.

To conform with how e.g. GNOME sets its margins.

This makes the code much cleaner, and easier to update.

Makes it easier to adjust the UI from a central place.

Makes it easier to adjust the UI from a central place.

Outlines are no longer commonly used. Instead visually separated
headlines are the norm.

Classical tabs are very dated. They are also a practical problem as you
get very limited in the numbers of tabs we can have, and how long the
text can be on them.

Switch to one popular modern model with a list on the left instead where
pages can be selected.

If the translations change then these files need to be regenerated as
they include data from those.