Create Package parser for font files

[JonoYang]

.ttf files have a good amount of origin information stored in them. We could create packages from font files since they can contain name, version, copyright, license, etc.

[pombredanne]

fonttools seems to be the tool.
There is a "name" section (which contains the metadata displayed with a font) with these ids that we may care for in the opentype/TTF metadata:

• copyright (nameID 0)
• familyName (nameID 1)
• styleName (nameID 2)
• uniqueFontIdentifier (nameID 3)
• fullName (nameID 4)
• version (nameID 5)
• psName (nameID 6)
• trademark (nameID 7)
• manufacturer (nameID 8)
• designer (nameID 9)
• description (nameID 10)
• vendorURL (nameID 11)
• designerURL (nameID 12)
• licenseDescription (nameID 13)
• licenseInfoURL (nameID 14)
• compatibleFullName (nameID 18)

See also these pointers:

• https://en.wikipedia.org/wiki/OpenType
• https://docs.microsoft.com/en-us/typography/opentype/spec/name
• https://exiftool.org/TagNames/Font.html#Name
• https://github.com/fonttools/fonttools
• https://pypi.org/project/font-v/
• https://github.com/fonttools/fonttools/blob/99743c14dff190176fbaaa5c8e94b5f7f53d4b2e/Lib/fontTools/subset/__init__.py#L251
• https://github.com/fonttools/fonttools/blob/8ab6af03c89726cf80ca3c4b755ae1bd0038b5da/Lib/fontTools/ufoLib/__init__.py#L1852
• https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/FontsPolicy
• There is some ISO standard
• https://github.com/tchollingsworth/ttname/blob/master/ttname/info.py
• See also https://font-bakery.readthedocs.io and Google Fonts renesune/Creative-Zoo-Sans#3 for some related linting
• https://github.com/googlefonts/gf-docs/tree/main/Spec ... there is even a schema for copyright statements https://github.com/googlefonts/gf-docs/tree/main/Spec#font-copyright
• https://silnrsi.github.io/FDBP/en-US/Copyright_and_Licensing.html
• https://unifiedfontobject.org/