Log message:
fontforge: align the block

Log message:
fontforge: explicitly don't build docs.

Log message:
fontforge: update to 20200314.

Significant changes include the following.

    FontForge now has much improved stroke expansion functionality. The main \ 
change is that it actually works most of the time. New features include support \ 
for arbitrary convex nibs and the miter-clip and arc join styles from SVG 2. All \ 
functionality is accessible from the Python and native APIs. (By @skef.)
    Remove overlap handles certain important edge cases better. (By @skef and \ 
@frank-trampe.)
    The Python API now has a function called genericGlyphChange that matches the \ 
"Change Glyph" command in the GUI. See #4133 for more details. (By \ 
@skef.)
    The Python API now has functions for getting Unicode script and for \ 
interrogating glyph boundaries. (By @ctrlcctrlv.)
    One can now use text flags (rather than just numerical flags) when opening a \ 
font file via the Python API. (By @skef.)
    UFO import now outputs the note field properly. (By @skef.)
    SVG import is much more robust. (By @skef.)
    We have dropped most gnulib and autotools logic in favor of CMake, which \ 
dramatically simplifies the build system and just as dramatically improves build \ 
time. (By @jtanx.)
    As part of the switch to CMake, per the deprecation of Python 2, and per the \ 
lack of objections to the proposal on the mailing list, we have dropped support \ 
for building FontForge with Python 2 support. The non-build-system Python 2 code \ 
remains, but it is neither tested nor maintained nor supported and is likely to \ 
follow a trajectory of decay and then removal.
    Documentation is now rendered in Sphinx, which makes maintenance and \ 
improvement easier. (By @jtanx.)
    Translations now happen on crowdin, which makes contributions easier. (By \ 
@jtanx.)
    We got such a contribution for Croatian. (By @milotype.)
    Character view point coloring is more consistent, and preview fills support \ 
transparency. (By @skef.)
    The user can now move and close tabs in the character view. (By @ctrlcctrlv.)
    The metrics view now allows for entry of negative kerning values and runs a \ 
bit more smoothly. (By @ctrlcctrlv.)
    There is now a warning when a user is about to discard an unsaved script. \ 
(By @ctrlcctrlv.)
    We fixed bugs all over, as always, with particular attention given to the \ 
metrics view, Python, Spiro, and high-resolution displays.

Notes on build system changes:

    libgutils and libgunicode have been combined into libfontforge
    libgdraw and libfontforgeexe have been combined into the fontforge \ 
executable itself
    No development files are installed (headers, or pkg-config). This is because \ 
we do not provide a stable API or ABI to work against, nor are the headers \ 
actually well configured to be used externally. We are also not aware of any \ 
maintained product that compiles against FontForge itself.

Log message:
*: revbump after fontconfig bl3 changes (libuuid removal)

Log message:
*: Apply revbump for graphics/giflib API change.

Log message:
Revbump for icu

Log message:
fontforge: python3.8 needs you to use the python3.8-embed pkg-config file.

Log message:
librsvg: update bl3.mk to remove libcroco in rust case

recursive bump for the dependency change

Log message:
*: recursive bump for libffi

Log message:
fontforge: Update to 20190801

Along with the usual bugfixes, there have been a couple of new features worth \ 
calling out:

    Added Croatian translation
    Added user decompositions
    New graphic for the splash/about screen
    Images embedded in SFDs are now serialised as PNGs
        This is enabled by default, but may be turned off with the \ 
'WritePNGInSFD' option.
        A new tag is used to identify this mode; 'Image2', instead of 'Image'
        This requires FontForge to be compiled with libpng support. If not \ 
compiled with libpng, FontForge will revert to the old method of serialising RLE \ 
encoded raw images.

As part of an ongoing effort to clean up the code base, there have additionally \ 
been multiple build system changes:

    Python 2 support is deprecated. It is strongly recommended to build with \ 
Python 3 support. Python 2 support will be removed in a future release.
    Both the Windows and Mac builds are now built with Python 3 instead of Python 2.
    The minimum supported version for the Mac build is now MacOS Sierra (10.12)
    FontForge no longer uses gnulib
    collab support has been removed
    The build system now expects libuninameslist to be present, and will fail if \ 
it is not found. Building without libuninameslist must be explcititly specified \ 
using --without-libuninameslist