New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TTFAutohint 'name' table details #1773
Comments
Sure! I'll do it :-D (I agree this is very important stuff) |
Is that a feature request, to highlight/track specific check results? |
I think it is just a feature request for a new check. But it might be a feature request for highlighting specific results on the dashboard if you decide to fill an issue at https://github.com/googlefonts/fontbakery-dashboard ;-) By the way, we do have a sketch of a metadata schema for check "priorities". But we never really tagged a significant amount of checks with these specific metadata fields. |
Yeah, and we don't use it all. If we decide to use it e.g. for this kind of thing, we may end up putting priorities on general checks that who are ours, but not those of other users ... In this case, the check is of course google fonts specific and the clash of priority preferences is far away of becoming real. |
I do not wish to over-complicate things here, but I acknowledge that priority-sorting seems like a user-specific setting rather than an absolute truth that is valid for everyone... |
And explicitly state why in the FAIL message. |
The current check only tries to parse ttfautohint version info, but not the args:
We probably would want to parse the args as well. |
It is critically important that all TTFs in the API have their TTFAutohint args in the 'name' table, so that an automated solution can be made to replicate the hinting on subsets, etc.
FB must therefore have a FAILing check for this (likely coded similar to the copyright notice check) and this is a high priority thing for the @graphicore dashboard to track across the publication flow for all families.
The text was updated successfully, but these errors were encountered: