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 | 15 | 16 | 67 | 7 | 136 |
0% | 8% | 9% | 36% | 4% | 73% |
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?
🔥 Forum-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]
DESCRIPTION.en_us.html should end in a linebreak.
⚠️ Forum-Regular.ttf
- ⚠️ WARN
The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]
Checking OS/2 achVendID.
⚠️ Forum-Regular.ttf
- ⚠️ WARN
OS/2 VendorID value 'pyrs' is not yet recognized. 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: unknown]
Check Google Fonts glyph coverage.
🔥 Forum-Regular.ttf
- 🔥 FAIL
Missing required codepoints:
- 0x0308 (COMBINING DIAERESIS) - 0x0132 (LATIN CAPITAL LIGATURE IJ) - 0x1E9E (LATIN CAPITAL LETTER SHARP S) - 0x0133 (LATIN SMALL LIGATURE IJ) - 0x0237 (LATIN SMALL LETTER DOTLESS J) - 0x00AA (FEMININE ORDINAL INDICATOR) - 0x00BA (MASCULINE ORDINAL INDICATOR) - 0x2212 (MINUS SIGN) - 0x0312 (COMBINING TURNED COMMA ABOVE) - 0x0326 (COMBINING COMMA BELOW) - 0x0327 (COMBINING CEDILLA) - 0x0328 (COMBINING OGONEK)
[code: missing-codepoints]
Check for codepoints not covered by METADATA subsets.
⚠️ Forum-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+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
- U+02CB MODIFIER LETTER GRAVE ACCENT: not included in any glyphset definition
- 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, coptic, cherokee
- U+0301 COMBINING ACUTE ACCENT: try adding one of: tai-le, tifinagh, coptic, cherokee
- U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, coptic, cherokee
- U+0303 COMBINING TILDE: not included in any glyphset definition
- U+0304 COMBINING MACRON: try adding one of: gothic, coptic, cherokee, tifinagh
- U+0306 COMBINING BREVE: try adding tifinagh
- U+0307 COMBINING DOT ABOVE: try adding one of: coptic, canadian-aboriginal, tifinagh, malayalam, tai-le
- 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+2015 HORIZONTAL BAR: 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
- U+2206 INCREMENT: not included in any glyphset definition
- U+2260 NOT EQUAL TO: not included in any glyphset definition
- U+2264 LESS-THAN OR EQUAL TO: not included in any glyphset definition
- U+2265 GREATER-THAN OR EQUAL TO: not included in any glyphset definition
- U+25CA LOZENGE: not included in any glyphset definition
- U+F6C3 : not included in any glyphset definition
- U+F6E1 : not included in any glyphset definition
Or you can add the above codepoints to one of the subsets supported by the font:
menu
,cyrillic
,cyrillic-ext
,latin
,latin-ext
[code: unreachable-subsetting]
Check license file has good copyright string.
🔥 Forum-Regular.ttf
- 🔥 FAIL
First line in license file is:
"copyright (c) 2011, denis masharov denis.masharov@gmail.com,"
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.
⚠️ Forum-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?
⚠️ Forum-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]
Description strings in the name table must not exceed 200 characters.
⚠️ Forum-Regular.ttf
- ⚠️ WARN
A few name table entries with ID=10 (NameID.DESCRIPTION) are longer than 200 characters. Please check whether those entries are copyright notices mistakenly stored in the description string entries by a bug in an old FontLab version. If that's the case, then such copyright notices must be removed from these entries. [code: too-long]
Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?
⚠️ Forum-Regular.ttf
- ⚠️ WARN
The gasp table has a range of 8 that may be unneccessary. [code: non-ffff-range]
- ⚠️ WARN
The gasp table has a range of 16 that may be unneccessary. [code: non-ffff-range]
- ⚠️ WARN
The gasp range 0xFFFF value 0x03 should be set to 0x0F. [code: unset-flags]
METADATA.pb subsets should be alphabetically ordered.
🔥 Forum-Regular.ttf
- 🔥 FAIL
METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'cyrillic', 'cyrillic-ext', 'latin', 'latin-ext'] and expected ['cyrillic', 'cyrillic-ext', 'latin', 'latin-ext', 'menu'] [code: not-sorted]
METADATA.pb font.filename and font.post_script_name fields have equivalent values?
🔥 Forum-Regular.ttf
- 🔥 FAIL
METADATA.pb font filename = "Forum-Regular.ttf" does not match post_script_name="Forum". [code: mismatch]
Copyright notices match canonical pattern in METADATA.pb
🔥 Forum-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 (c) 2011, denis masharov denis.masharov@gmail.com. this font software is licensed under the sil open font license, version 1.1. this license is available with a faq at: http://scripts.sil.org/ofl" [code: bad-notice-format]
Copyright notices match canonical pattern in fonts
🔥 Forum-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 (c) 2011, Denis Masharov denis.masharov@gmail.com. This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL" [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 (c) 2011, Denis Masharov denis.masharov@gmail.com. This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL" [code: bad-notice-format]
METADATA.pb weight matches postScriptName for static fonts.
🔥 Forum-Regular.ttf
- 🔥 FAIL
METADATA.pb: Mismatch between postScriptName ("Forum") and weight value (400). The name must be ended with "Regular" or "Italic".
METADATA.pb: Check URL on copyright string is the same as in repository_url field.
🔥 Forum-Regular.ttf
- 🔥 FAIL
Value of repository_url field is
But font copyright string has: http://scripts.sil.org/OFL [code: mismatch]
Check font names are correct
🔥 Forum-Regular.ttf
- 🔥 FAIL
Font names are incorrect:
| nameID | current | expected | | :--- | :--- | :--- | | Family Name | Forum | Forum | | Subfamily Name | Regular | Regular | | Full Name | Forum | Forum Regular | | Poscript Name | Forum | Forum-Regular | [code: bad-names]
- ⚠️ WARN
Regular missing from full name [code: lacks-regular]
Font enables smart dropout control in "prep" table instructions?
🔥 Forum-Regular.ttf
- 🔥 FAIL
The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the
gftools fix-nonhinting
script. [code: lacks-smart-dropout]
A static fonts directory with at least two fonts must accompany variable fonts
⚠️ Forum-Regular.ttf
- ⚠️ WARN
Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]
On a family update, the DESCRIPTION.en_us.html file should ideally also be updated.
⚠️ Forum-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]
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) is set in all fonts.
🔥 Forum-Regular.ttf
- 🔥 FAIL
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/forum/Forum-Regular.ttf']. [code: missing-os2-fsselection-bit7]
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ Forum-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?
🔥 Forum-Regular.ttf
- 🔥 FAIL
The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
Check font contains no unreachable glyphs
⚠️ Forum-Regular.ttf
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- NULL - nonmarkingreturn - uni0416.alt - uni041A.alt - uni0436.alt - uni043A.alt
[code: unreachable-glyphs]
Check if each glyph has the recommended amount of contours.
⚠️ Forum-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: uni01F5 Contours detected: 4 Expected: 3 - Glyph name: uni00AD Contours detected: 1 Expected: 0
[code: contour-count]
Does the font contain a soft hyphen?
⚠️ Forum-Regular.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
Check math signs have the same width.
⚠️ Forum-Regular.ttf
- ⚠️ WARN
The most common width is 467 among a set of 10 math glyphs. The following math glyphs have a different width, though:
Width = 495: divide [code: width-outliers]
Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)
⚠️ Forum-Regular.ttf
- ⚠️ WARN
Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
dcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
tcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
Section: fontbakery.profiles.name
🔥⏩⏩Description strings in the name table must not contain copyright info.
🔥 Forum-Regular.ttf
- 🔥 FAIL
Some namerecords with ID=10 (NameID.DESCRIPTION) containing copyright info should be removed (perhaps these were added by a longstanding FontLab Studio 5.x bug that copied copyright notices to them.) [code: copyright-on-description]
Section: fontbakery.profiles.kern
🔥Is there a usable "kern" table declared in the font?
🔥 Forum-Regular.ttf
- 🔥 FAIL
The following glyphs should not be used in the "kern" table because they are not in the "cmap" table: uni041A.alt, uni0436.alt, uni043A.alt [code: kern-non-character-glyphs]
Section: Shaping Checks
⚠️⏩⏩⏩⏩Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
⚠️ Forum-Regular.ttf
- ⚠️ WARN
The dot of soft dotted characters used in orthographies must disappear in the following strings: i̊ i̋ j̀ j́ j̃ j̄ į̀ į́ į̂ į̃ į̄ į̌ і́
The dot of soft dotted characters should disappear in other cases, for example: i̇ ǐ j̆ j̇ j̊ j̋ ǰ į̆ į̇ į̊ į̋ і̀ і̂ і̃ і̄ і̆ і̇ і̊ і̋ і̌
Your font does not cover the following languages that require the soft-dotted feature: Basaa (Latn, 332,940 speakers), Igbo (Latn, 27,823,640 speakers), Lithuanian (Latn, 2,357,094 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Dutch (Latn, 31,709,104 speakers), Belarusian (Cyrl, 10,064,517 speakers), Navajo (Latn, 166,319 speakers), Aghem (Latn, 38,843 speakers). [code: soft-dotted]