Improved content and layout of OFL button and tooltips (fixed the repeated lines)
Make text lighter and more in tune with practical steps
Added missing newline
Add some comments relevant to class kerning.
Add support for import and export of U. F. O. groups and group kerning rules.
Python minor cleanups

Noticed redundant #ifndef's during investigation of #1756.  Since almost
all code within fontforge/python.c is surrounded by `#ifndef _NO_PYTHON`
it was strange to see individual bits of code surrounded by additional
such `#ifndefs`

Also, one copy-n-paste was one line too low, with an `exit(0)` before it.

And just happened to notice an extra unneeded declaration in
fontforgeexe/startui.c  Do modern C compilers just drop those?  And wow,
Coverity didn't complain either.
Python Py_BuildValue() bad zero values

Reading through old changes to fontforge/python.c I saw change 94b6ccb9484eb85fe25c5e127ce33175e1118a67
which intrigued me, telling me something I didn't know about using the
Python C API Py_BuildValue().  His descriptions included
> Integers being incorrectly passed to Py_BuildValue() expecting double.
>   The fix is to substitute 0.0 for 0 in these arguments, which C treats
>   as constant of type double.

But when you find one instance of a bad pattern, you should worry
whether that same goof was reproduced in multiple.  (Un?)fortunately
this same mistake was found in 3 more places.  These were changed
like this:
>     return( Py_BuildValue("(dddd)", 0,0,0,0 ));

to
>     return( Py_BuildValue("(dddd)", 0.0, 0.0, 0.0, 0.0 ));

One instance was easily tested, and indeed found to be broken and then
fixed by this change:
>  contour.boundingBox() returned '(6.91320453175617e-310, 6.91320569035315e-310, 6.9132056837544e-310, 1e-323)'

vs.
>  contour.boundingBox() returned '(0.0, 0.0, 0.0, 0.0)'
Merge pull request #1766 from tshinnic/python_cleanup_misc_1

Python cleanup misc 1
Adjust Red Hat packaging metadata in order to support new rules on file inclusion.
Merge pull request #1767 from fontforge/frank_redhat_2

Conform Red Hat packaging metadata to new rules.
Remove more absolute symlinks from the source tree.
Add missing destructors.
Merge pull request #1768 from fontforge/frank_redhat_2

Remove more absolute symlinks from the source tree.
Update Ukrainian translation
Merge pull request #1772 from yurchor/master

Update Ukrainian translation
Improve help string for ResourceFile preference
Merge pull request #1773 from rrthomas/master

Improve help string for ResourceFile preference
Remove HelpDir preference

There’s no need for this: help should always be installed in the right
place for the given build. We should not encourage FF to be installed
without help files, even if this will sometimes happen (e.g. when it’s
packaged, but in that case I’d expect a corresponding -doc package that
installs the help in the right place).

(Suppose a user on an increasingly-mythical multiuser system whose
sysadmin has installed FF but not the help files: in that case, let that
user install their own copy of FF, then they can be sure the help files
they install will actually match it.)
Fix #1769: don't set ResourceFile pref unless user does so explicitly
Merge pull request #1774 from rrthomas/master

Remove HelpDir preference; fix ResourceFile fallback (#1769)