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
[gftools-packager] Urbanist: Version 1.250 added #3431
[gftools-packager] Urbanist: Version 1.250 added #3431
Conversation
coreyhu
commented
May 20, 2021
- Urbanist Version 1.250 taken from the upstream repo https://github.com/coreyhu/Urbanist at commit coreyhu/Urbanist@848dc17.
* Urbanist Version 1.250 taken from the upstream repo https://github.com/coreyhu/Urbanist at commit coreyhu/Urbanist@848dc17.
Hi @RosaWagner this is a followup to #3418 which is now closed. There've been some updates and the fontbakery checks on the static files should now all pass. The variable file uses an Apologies, are you able to re-add it to the pipeline? |
@coreyhu wow this is amazing work!! I've approved this for @RosaWagner to merge once any issues she finds are resolved |
LGTM. Let's get this into production. Thanks @coreyhu! |
I've removed the ital axis since older versions of firefox/chrome have patchy support. We will reenable the axis once these browsers are used by less people. |
Sounds good! Let me know if any additional changes are necessary. Will the italics still be available as static files? |
Wait wait wait before merging. There are still some stuff to correct, like the OFL, which is missing a part in the header. @coreyhu contact me by email to arrange a call, so I can also explain the different choices for the ital axis. |
Thanks, the OFL header has been updated and I sent you an email to follow up. Let me know if there's any additional changes that need to be made! |
Hi all, I made the following changes:
Please let me know if any other changes are necessary |
Base letters (and comb accents) don't have anchors. Sorry I missed that earlier. This check is still not implemented in FB but will come. |
Fontbakery reportFontbakery version: 0.7.37 [8] Urbanist-Italic[wght].ttf🔥 FAIL: Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.
🔥 FAIL: METADATA.pb font.full_name value matches fullname declared on the name table?
🔥 FAIL: METADATA.pb font.style "italic" matches font internals?
🔥 FAIL: METADATA.pb font.name and font.full_name fields match the values declared on the name table?
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?
⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts--- Rationale --- Variable font family directories kept in the google/fonts git repo may include a static/ subdir containing static fonts. These files are meant to be served for users that still lack support for variable fonts in their web browsers.
⚠ WARN: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?
⚠ WARN: Are there any misaligned on-curve points?
--- Rationale --- This check heuristically looks for on-curve points which are close to, but do not sit on, significant boundary coordinates. For example, a point which has a Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the baseline, here we also check for points near the x-height (but only for lower case Latin letters), cap-height, ascender and descender Y coordinates. Not all such misaligned curve points are a mistake, and sometimes the design may call for points in locations near the boundaries. As this check is liable to generate significant numbers of false positives, it will pass if there are more than 100 reported misalignments.
[4] Urbanist[wght].ttf⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?
⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts--- Rationale --- Variable font family directories kept in the google/fonts git repo may include a static/ subdir containing static fonts. These files are meant to be served for users that still lack support for variable fonts in their web browsers.
⚠ WARN: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?
⚠ WARN: Are there any misaligned on-curve points?
--- Rationale --- This check heuristically looks for on-curve points which are close to, but do not sit on, significant boundary coordinates. For example, a point which has a Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the baseline, here we also check for points near the x-height (but only for lower case Latin letters), cap-height, ascender and descender Y coordinates. Not all such misaligned curve points are a mistake, and sometimes the design may call for points in locations near the boundaries. As this check is liable to generate significant numbers of false positives, it will pass if there are more than 100 reported misalignments.
Summary
Note: The following loglevels were omitted in this report:
|
Side note: for this PR we are waiting for fonttools to fix the problem with the name ID25 : fonttools/fonttools#2336 |
Would there be an issue with adding a step in the build workflow to correct nameID 25 after running VarLib Instancer? |
You can do so :) |
Enjoy the break! Meanwhile, nameID 25 should now be updated. Is someone able to check it out? Thanks in advance! |
Finally got around to writing the postprocessing script for updating the name table. I believe this should match Texturina |
Author corrected the name ID 25 with a script after slicing Roman/Italic with Fonttools, so I doubled check in Indesign and it works fine :) LGTM Fontbakery reportFontbakery version: 0.7.37 [1] Family checks🔥 FAIL: Do we have the latest version of FontBakery installed?
[1] Urbanist-Italic[wght].ttf⚠ WARN: Are there any misaligned on-curve points?
--- Rationale --- This check heuristically looks for on-curve points which are close to, but do not sit on, significant boundary coordinates. For example, a point which has a Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the baseline, here we also check for points near the x-height (but only for lower case Latin letters), cap-height, ascender and descender Y coordinates. Not all such misaligned curve points are a mistake, and sometimes the design may call for points in locations near the boundaries. As this check is liable to generate significant numbers of false positives, it will pass if there are more than 100 reported misalignments.
[1] Urbanist[wght].ttf⚠ WARN: Are there any misaligned on-curve points?
--- Rationale --- This check heuristically looks for on-curve points which are close to, but do not sit on, significant boundary coordinates. For example, a point which has a Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the baseline, here we also check for points near the x-height (but only for lower case Latin letters), cap-height, ascender and descender Y coordinates. Not all such misaligned curve points are a mistake, and sometimes the design may call for points in locations near the boundaries. As this check is liable to generate significant numbers of false positives, it will pass if there are more than 100 reported misalignments.
Summary
Note: The following loglevels were omitted in this report:
Urbanist_QA.zip |