-
Notifications
You must be signed in to change notification settings - Fork 105
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
Request for feedback: Proposal of reorganization of profiles #4801
Milestone
Comments
Broadly I support this work |
Merged
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Aug 8, 2024
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Aug 8, 2024
felipesanches
added a commit
that referenced
this issue
Aug 8, 2024
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Aug 9, 2024
The UFO profile was removed and its checks were migrated to the Universal profile. For that reason, all of them received a temporary "experimental" flag. Those checks will only run when actual UFO projects are passed to fontbakery. (issue fonttools#4801)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Aug 9, 2024
The Shaping profile was also removed and its checks migrated to the Google Fonts profile. As gfonts was already including those, and no other profile did so, there's no need to add experimental flags to these ones. (issue fonttools#4801)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Aug 9, 2024
The Outline profile was also removed and its checks migrated to the Google Fonts profile. As gfonts was already including those, and no other profile did so, there's no need to add experimental flags to these ones. (issue fonttools#4801)
felipesanches
added a commit
to felipesanches/fontbakery
that referenced
this issue
Aug 9, 2024
The Outline profile was also removed and its checks migrated to the Google Fonts profile. As gfonts was already including those, and no other profile did so, there's no need to add experimental flags to these ones. (issue fonttools#4801)
felipesanches
added a commit
that referenced
this issue
Aug 9, 2024
The UFO profile was removed and its checks were migrated to the Universal profile. For that reason, all of them received a temporary "experimental" flag. Those checks will only run when actual UFO projects are passed to fontbakery. (issue #4801)
felipesanches
added a commit
that referenced
this issue
Aug 9, 2024
The Shaping profile was also removed and its checks migrated to the Google Fonts profile. As gfonts was already including those, and no other profile did so, there's no need to add experimental flags to these ones. (issue #4801)
felipesanches
added a commit
that referenced
this issue
Aug 9, 2024
The Outline profile was also removed and its checks migrated to the Google Fonts profile. As gfonts was already including those, and no other profile did so, there's no need to add experimental flags to these ones. (issue #4801)
OK... Now what to do about the rest? I think I'll treat |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we have these profiles:
We can categorize them this way:
Generaly useful ones:
Vendor specific profiles:
Profile defined by file-type:
Profiles defined by aspect of problems being checked for:
outliers:
I think that we should reorganize the profiles to be categorized strictly by vendor needs. It means that we should fit everything into either "Generaly useful profiles" or "Vendor specific profiles".
So, for instance, UFO checks should be assigned to either vendor-specific profiles or to the Universal one.
Same reasoning for shaping and outline.
Maybe we should drop support for fontval. Or, maybe, the check could be included in the Microsoft profile.
I think it won't be too hard to include notofonts related checks in the GoogleFonts profile and simply check Noto families with the GFonts profile.
The only one here that I am still a bit uncertain is the iso15008 one. Not sure if we should have a special way to enable/disable that kind of profile, as it definitely does not apply to all font families (so it can't be considered universal), but it is also not vendor-specific. This one sounds legitimately optional.
The text was updated successfully, but these errors were encountered: