Fontbakery Technical Report

If you think a check is flawed or have an idea for a check, please file an issue at https://github.com/googlefonts/fontbakery/issues and remember to include a pointer to the repo and branch you're checking.

Summary

💥 ERROR	🔥 FAIL	⚠️ WARN	⏩ SKIP	ℹ️ INFO	✅ PASS
0	1	7	113	7	105
0%	1%	4%	64%	4%	59%

Note: The following loglevels were omitted in this report: SKIP, INFO, PASS, DEBUG

<Section: Google Fonts> 🔥⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️ℹ️

Is there kerning info for non-ligated sequences?

Check ID: <FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN

GPOS table lacks kerning info for the following non-ligated sequences:

- u10B00 + u10B35

- u10B31 + u10B00

- u10B00 + u10B17 

- And u10B17 + u10B19 [code: lacks-kern-info]

Ensure fonts have ScriptLangTags declared on the 'meta' table.

Check ID: <FontBakeryCheck:com.google.fonts/check/meta/script_lang_tags>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]

Noto fonts must have an ARTICLE.en_us.html file

Check ID: <FontBakeryCheck:com.google.fonts/check/description/noto_has_article>

🔥 fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

🔥 FAIL
This is a Noto font but it lacks an ARTICLE.en_us.html file [code: missing-article]

<Section: Universal> ⚠️⚠️⏩⏩⏩⏩⏩⏩ℹ️ℹ️

Check font contains no unreachable glyphs

Check ID: <FontBakeryCheck:com.google.fonts/check/unreachable_glyphs>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
```
- periodcentered 

- And uni00A0.1
```
[code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN
This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:
```
- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2 

- And Glyph name: uogonek	Contours detected: 2	Expected: 1
```
[code: contour-count]

<Section: fontbakery.profiles.gdef> ⚠️

Check mark characters are in GDEF mark glyph class.

Check ID: <FontBakeryCheck:com.google.fonts/check/gdef_mark_chars>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN
The following mark characters could be in the GDEF mark glyph class: acutecomb (U+0301), gravecomb (U+0300), tildecomb (U+0303), uni0302 (U+0302), uni0304 (U+0304), uni0306 (U+0306), uni0307 (U+0307), uni0308 (U+0308), uni030A (U+030A), uni030B (U+030B) and 5 more.

Use -F or --full-lists to disable shortening of long lists. [code: mark-chars]

<Section: Outline Correctness Checks> ⚠️⚠️

Are any segments inordinately short?

Check ID: <FontBakeryCheck:com.google.fonts/check/outline_short_segments>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN

The following glyphs have segments which seem very short:

* two (U+0032) contains a short segment L<<159.0,84.0>--<159.0,80.0>>

* at (U+0040) contains a short segment B<<613.0,293.0>-<612.0,275.0>-<612.0,267.5>>

* at (U+0040) contains a short segment B<<612.0,267.5>-<612.0,260.0>-<612.0,257.0>>

* M (U+004D) contains a short segment L<<177.0,626.0>--<173.0,626.0>>

* M (U+004D) contains a short segment L<<450.0,129.0>--<454.0,129.0>>

* N (U+004E) contains a short segment L<<176.0,593.0>--<172.0,593.0>>

* N (U+004E) contains a short segment L<<582.0,123.0>--<586.0,123.0>>

* Q (U+0051) contains a short segment B<<416.0,-9.0>-<410.0,-9.0>-<403.5,-9.5>>

* Q (U+0051) contains a short segment B<<403.5,-9.5>-<397.0,-10.0>-<391.0,-10.0>>

* W (U+0057) contains a short segment B<<468.0,577.5>-<463.0,600.0>-<461.0,609.0>> 

* And 83 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

Do outlines contain any jaggy segments?

Check ID: <FontBakeryCheck:com.google.fonts/check/outline_jaggy_segments>

⚠️ fonts/NotoSansAvestan/googlefonts/ttf/NotoSansAvestan-Regular.ttf

⚠️ WARN

The following glyphs have jaggy segments:

* u10B04 (U+10B04): B<<183.0,355.0>-<202.0,304.0>-<206.0,247.0>>/B<<206.0,247.0>-<231.0,438.0>-<384.0,438.0>> = 11.47123083564637 

* And u10B04 (U+10B04): B<<239.5,3.0>-<211.0,68.0>-<206.0,148.0>>/B<<206.0,148.0>-<199.0,81.0>-<181.0,16.0>> = 9.540821476250422 [code: found-jaggy-segments]