If you think a check is flawed or have an idea for a check, please file an issue at https://github.com/fonttools/fontbakery/issues and remember to include a pointer to the repo and branch you're checking.
Summary
💥 ERROR | 🔥 FAIL | ⚠️ WARN | ⏩ SKIP | ℹ️ INFO | ✅ PASS |
---|---|---|---|---|---|
0 | 9 | 16 | 63 | 8 | 145 |
0% | 5% | 9% | 36% | 5% | 82% |
Note: The following loglevels were omitted in this report: SKIP, INFO, PASS, DEBUG
Meaning of check results:
- 💥 An ERROR is something wrong with FontBakery itself, possibly a bug.
- 🔥 A FAIL is a problem with the font that must be fixed.
- ⚠️ A WARN is something that you should consider addressing.
- ℹ️ An INFO result simply prints something useful. Typically stats.
- ✅ A PASS means the font looks good for the given checking routine.
- ⏩ And a SKIP happens when the check does not apply to the given font.
If you get ERRORs, please help us improve the tool by reporting them at our issue tracker.
(but other kinds of bug reports and/or feature requests are also always welcome, of course!)
FontBakery version: 0.9.2
Section: Google Fonts
🔥🔥🔥🔥🔥🔥🔥⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️Does DESCRIPTION file contain a upstream Git repo URL?
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
Please host your font project on a public Git repo (such as GitHub or GitLab) and place a link in the DESCRIPTION.en_us.html file. [code: lacks-git-url]
Checking OS/2 achVendID.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
OS/2 VendorID is 'PfEd', a font editor default. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]
Check Google Fonts glyph coverage.
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
Missing required codepoints:
- 0x0126 (LATIN CAPITAL LETTER H WITH STROKE) - 0x0132 (LATIN CAPITAL LIGATURE IJ) - 0x014A (LATIN CAPITAL LETTER ENG) - 0x1E9E (LATIN CAPITAL LETTER SHARP S) - 0x014B (LATIN SMALL LETTER ENG) - 0x2212 (MINUS SIGN) - 0x0312 (COMBINING TURNED COMMA ABOVE)
[code: missing-codepoints]
Check for codepoints not covered by METADATA subsets.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.
- U+02C7 CARON: try adding one of: tifinagh, canadian-aboriginal
- U+02D8 BREVE: try adding canadian-aboriginal
- U+02D9 DOT ABOVE: try adding canadian-aboriginal
- U+02DB OGONEK: try adding canadian-aboriginal
- U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
- U+0300 COMBINING GRAVE ACCENT: try adding one of: tai-le, cherokee, coptic
- U+0301 COMBINING ACUTE ACCENT: try adding one of: tai-le, tifinagh, cherokee, coptic
- U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, cherokee, coptic
- U+0303 COMBINING TILDE: not included in any glyphset definition
- U+0304 COMBINING MACRON: try adding one of: gothic, tifinagh, cherokee, coptic
- U+0306 COMBINING BREVE: try adding tifinagh
- U+0307 COMBINING DOT ABOVE: try adding one of: malayalam, canadian-aboriginal, tifinagh, tai-le, coptic
- U+0308 COMBINING DIAERESIS: try adding one of: gothic, tai-le, coptic
- U+0309 COMBINING HOOK ABOVE: try adding tifinagh
- U+030A COMBINING RING ABOVE: not included in any glyphset definition
- U+030B COMBINING DOUBLE ACUTE ACCENT: try adding cherokee
- U+030C COMBINING CARON: try adding one of: tai-le, cherokee
- U+031B COMBINING HORN: not included in any glyphset definition
- U+0323 COMBINING DOT BELOW: try adding one of: tifinagh, malayalam, cherokee, coptic
- U+0326 COMBINING COMMA BELOW: not included in any glyphset definition
- U+0327 COMBINING CEDILLA: not included in any glyphset definition
- U+0328 COMBINING OGONEK: not included in any glyphset definition
- U+0335 COMBINING SHORT STROKE OVERLAY: not included in any glyphset definition
- U+2021 DOUBLE DAGGER: not included in any glyphset definition
- U+2030 PER MILLE SIGN: not included in any glyphset definition
Or you can add the above codepoints to one of the subsets supported by the font:
cyrillic
,cyrillic-ext
,latin
,latin-ext
,menu
,vietnamese
[code: unreachable-subsetting]
Check license file has good copyright string.
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
First line in license file is:
"copyright 2012 the yeseva one project authors (lemonad@jovanny.ru), with reserved font name "yeseva"."
which does not match the expected format, similar to:
"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]
Check copyright namerecords match license file.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
License URL matches License text on name table?
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
Copyright notices match canonical pattern in METADATA.pb
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
METADATA.pb: Copyright notices should match a pattern similar to: "Copyright 2020 The Familyname Project Authors (git url)" But instead we have got: "copyright 2012 the yeseva one project authors (lemonad@jovanny.ru), with reserved font name "yeseva"." [code: bad-notice-format]
Copyright notices match canonical pattern in fonts
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright 2012 The Yeseva One Project Authors (lemonad@jovanny.ru), with Reserved Font Name "Yeseva"." [code: bad-notice-format]
- 🔥 FAIL
Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright 2012 The Yeseva One Project Authors (lemonad@jovanny.ru), with Reserved Font Name "Yeseva"." [code: bad-notice-format]
Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
METADATA.pb: copyright field ("Copyright 2012 The Yeseva One Project Authors (lemonad@jovanny.ru), with Reserved Font Name "Yeseva".") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]
PPEM must be an integer on hinted fonts.
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into an integer value.
This can be accomplished by using the 'gftools fix-hinting' command:
# create virtualenv python3 -m venv venv # activate virtualenv source venv/bin/activate # install gftools pip install git+https://www.github.com/googlefonts/tools
[code: bad-flags]
Name table strings must not contain the string 'Reserved Font Name'.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name ("Yeseva") that differs from the currently used family name (YesevaOne), which is fine. [code: legacy-familyname]
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name ("Yeseva") that differs from the currently used family name (YesevaOne), which is fine. [code: legacy-familyname]
A static fonts directory with at least two fonts must accompany variable fonts
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]
Ensure METADATA.pb does not use escaped strings.
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
Found escaped chars at 'Copyright 2012 The Yeseva One Project Authors (lemonad@jovanny.ru), with Reserved Font Name '. Please use an unicode string instead. [code: escaped-strings]
On a family update, the DESCRIPTION.en_us.html file should ideally also be updated.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
The DESCRIPTION.en_us.html file in this family has not changed in comparison to the latest font release on the google/fonts github repo. Please consider mentioning note-worthy improvements made to the family recently. [code: description-not-updated]
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
Section: Universal
🔥🔥⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩ℹ️ℹ️Font contains '.notdef' as its first glyph?
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
Check font contains no unreachable glyphs
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- NULL - foundryicon
[code: unreachable-glyphs]
Check if each glyph has the recommended amount of contours.
⚠️ YesevaOne-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: uni00AD Contours detected: 1 Expected: 0 - Glyph name: hcircumflex Contours detected: 1 Expected: 2 - Glyph name: lacute Contours detected: 1 Expected: 2 - Glyph name: hcircumflex Contours detected: 1 Expected: 2 - Glyph name: lacute Contours detected: 1 Expected: 2 - Glyph name: uni00AD Contours detected: 1 Expected: 0
[code: contour-count]
Does the font contain a soft hyphen?
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
Check math signs have the same width.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
The most common width is 505 among a set of 3 math glyphs. The following math glyphs have a different width, though:
Width = 515: plus
Width = 460: equal
Width = 470: logicalnot
Width = 406: multiply
Width = 500: divide [code: width-outliers]
Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)
🔥 YesevaOne-Regular.ttf
- 🔥 FAIL
Lcaron uses component uni030C. [code: wrong-mark]
Section: fontbakery.profiles.dsig
⚠️Does the font have a DSIG table?
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
This font has a digital signature (DSIG table) which is only required - even if only a placeholder - on old programs like MS Office 2013 in order to work properly. The current recommendation is to completely remove the DSIG table. [code: found-DSIG]
Section: Shaping Checks
⚠️⚠️⏩⏩⏩Ensure dotted circle glyph is present and can attach marks.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
No dotted circle glyph present [code: missing-dotted-circle]
Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
⚠️ YesevaOne-Regular.ttf
- ⚠️ WARN
The dot of soft dotted characters used in orthographies must disappear in the following strings: į̀ į́ į̂ į̃ į̄ į̌ і́ ị̀ ị́ ị̂ ị̃ ị̄
The dot of soft dotted characters should disappear in other cases, for example: i̦̇ i̦̊ i̦̋ ǐ̦ j̦̀ j̦́ j̦̃ j̦̄ j̦̆ j̦̇ j̦̈ j̦̉ j̦̊ j̦̋ ǰ̦ į̆ į̇ į̈ į̉ į̊
Your font fully covers the following languages that require the soft-dotted feature: Igbo (Latn, 27,823,640 speakers), Dutch (Latn, 31,709,104 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Basaa (Latn, 332,940 speakers), Lithuanian (Latn, 2,357,094 speakers), Belarusian (Cyrl, 10,064,517 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Aghem (Latn, 38,843 speakers), Navajo (Latn, 166,319 speakers). [code: soft-dotted]