Open felipesanches opened 6 years ago
Regarding https://github.com/google/fonts/issues/1539 , we would have to keep it in a nice-to-have category for a while, until we consider it reasonable to demand that all families on the Google Fonts collection must have those example strings. Deciding where to switch from recommendation
(nice-to-have) to requirement
(must-have) is subtle, but having a proper way to mark it up will make it easier to track these aspects of the collection.
@davelab6 is this aligned with your expectations regarding higher-quality font projects and ways of monitoring their progress?
FontBakery nowadays focuses on getting a collection of families to a good quality state by getting a 100% PASS on our current checks.
But then we may want to add checks that are not required to pass on all font projects but that would be indicators of higher levels of quality (such as evaluating glyph coverage of larger glyph-sets for specific scripts/languages).
Or even checks for things like https://github.com/google/fonts/issues/1539 (having example strings for all opentype features implemented in a font).