`name` table issues due to buggy FontForge based build

[Nigelw]

Love your work on this font. Heads up about a small issue. When I add the Style B ttf to my Mac using Font Book, I get an error on import:

The other TTFs are fine, it's only this one which throws up a warning like this. I don't know much about font file structures so am not sure if this is worthy of a fix, but wanted to give a heads up.

[kenmcd]

All the fonts have name issues.
Surprised that is the only one flagged.
The Full Font Name is not the "full font name" in all the Regulars.
And all the Italics have the style-link set to Bold, which is probably what is causing Issue #15

[ctrlcctrlv]

This font needs rebuilding from its masters, I know. I apologize for name table issues. This is one of my older fonts, and was the last one I built via a legacy, deprecated method (FontForge direct OTF creation).

It's worth mentioning that my fonts are best tested on GNU/Linux, which uses fontconfig, not whatever macOS or Windows does for that, and that's how this issue got into the releases.

I have made some progress towards moving this over to a UFO fontmake-based build…but that's not happening this week. I have a major release to make tomorrow, of FRB Amercan Cursive v2/FRB American Print v1. I'll figure out when I'm working on v1 of this font after that. This font is still technically not in v1, and this name issue is one big reason why.

[ctrlcctrlv]

The most recent release was not even a complete rebuild, because a complete rebuild is no longer possible without some serious work to recreate my old environment. You'd need an old patched FontForge, etc.

The last release just patched name and fixed a critical bug in GSUB:

https://github.com/ctrlcctrlv/TT2020/blob/master/build/version_0.2_patch.py

I guess another script like this could patch name again, but obviously what we really need is a way to do full builds again. :)