search

xconsau / KumbhSans

SIL Open Font License 1.1
68 stars 1 forks source link

FB report #7

Closed RosaWagner closed 3 years ago

RosaWagner commented 3 years ago

Fontbakery report

Fontbakery version: 0.7.35

[1] Family checks
🔥 FAIL: Do we have the latest version of FontBakery installed? * [com.google.fonts/check/fontbakery_version](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/fontbakery_version) * 🔥 **FAIL** Current Font Bakery version is 0.7.35, while a newer 0.7.36 is already available. Please upgrade it with 'pip install -U fontbakery'

[3] KumbhSans[opsz,wght].ttf
🔥 FAIL: Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts. * [com.google.fonts/check/vertical_metrics_regressions](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vertical_metrics_regressions) 
--- Rationale ---
If the family already exists on Google Fonts, we need to ensure that the checked
family's vertical metrics are similar. This check will test the following schema
which was outlined in Fontbakery issue #1162 [1]:
- The family should visually have the same vertical metrics as the Regular style
hosted on Google Fonts.
- If the family on Google Fonts has differing hhea and typo metrics, the family
being checked should use the typo metrics for both the hhea and typo entries.
- If the family on Google Fonts has use typo metrics not enabled and the family
being checked has it enabled, the hhea and typo metrics should use the family on
Google Fonts winAscent and winDescent values.
- If the upms differ, the values must be scaled so the visual appearance is the
same.
[1] https://github.com/googlefonts/fontbakery/issues/1162
* 🔥 **FAIL** Kumbh Sans Regular: OS/2 sTypoAscender is 2045 when it should be 1540 [code: bad-typo-ascender] * 🔥 **FAIL** Kumbh Sans Regular: hhea Ascender is 2045 when it should be 1540 [code: bad-hhea-ascender]
🔥 FAIL: Validate STAT particle names and values match the fallback names in GFAxisRegistry. * [com.google.fonts/check/STAT/gf-axisregistry](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/STAT/gf-axisregistry) 
--- Rationale ---
Check that particle names and values on STAT table match the fallback names in
each axis entry at the Google Fonts Axis Registry, available at
https://github.com/google/fonts/tree/main/axisregistry
* 🔥 **FAIL** STAT table is missing Axis Value Records [code: missing-axis-values]
🔥 FAIL: Ensure variable fonts include an avar table. * [com.google.fonts/check/mandatory_avar_table](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/mandatory_avar_table) 
--- Rationale ---
Most variable fonts should include an avar table to correctly define axes
progression rates.
For example, a weight axis from 0% to 100% doesn't map directly to 100 to 1000,
because a 10% progression from 0% may be too much to define the 200, while 90%
may be too little to define the 900.
If the progression rates of axes is linear, this check can be ignored. Fontmake
will also skip adding an avar table if the progression rates are linear.
However, we still recommend designers visually proof each instance is at the
desired weight, width etc.
* 🔥 **FAIL** This variable font does not have an avar table. [code: missing-avar]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 4 0 97 8 95 0
0% 2% 0% 48% 4% 47% 0%

Note: The following loglevels were omitted in this report:

Please download: QA.zip

RosaWagner commented 3 years ago

These 3 fails need to be fixed, we'll discuss it during our call tomorrow :)