Does Fontspector already contain the full set of public Font Bakery checks?

[arrowtype]

Does Fontspector already contain the full set of public Font Bakery checks?

If it leaves any out, which ones, and why? If there is a roadmap, is that available?

If it has already ported 100% of the checks (which appears may be the case), would that perhaps make sense to include somewhere in the Readme?

Thanks for any insights!

[simoncozens]

It leaves out one check - shaping/regression - because I thought I was the only person who used it. I've since found out that other people are, so I plan to port that one as well. But otherwise it's complete. I thought that was implicit in the fact that we have a 1.0.0 version number. :-) But it would be good to make it explicit as well.

Incidentally, Google Fonts switched from Fontbakery to Fontspector for our production use in May and it's been fine...

[devosb]

I am finding that a number of checks in Font Bakery have not been ported to Fontspector, not just shaping/regression mentioned above, such as

• The checks starting with designspace_ are not in Fontspector, although they are mentioned in something like a roadmap.
• Checks such as fontwerk/style_linking and typenetwork/weightclass are missing, but I suspect what they check for is already handled by other checks.
• typenetwork/family/valid_underline There are other checks in Fontspector to look at underline values, but from reading the code seem to check for something a bit different.
• notofonts/unicode_range_bits This functionality seems to be completely missing in Fontspector.