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 | 11 | 16 | 66 | 8 | 140 |
0% | 6% | 9% | 39% | 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?
🔥 Ledger-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.
⚠️ Ledger-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.
⚠️ Ledger-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.
🔥 Ledger-Regular.ttf
- 🔥 FAIL
Missing required codepoints:
- 0x0308 (COMBINING DIAERESIS) - 0x0300 (COMBINING GRAVE ACCENT) - 0x0301 (COMBINING ACUTE ACCENT) - 0x030B (COMBINING DOUBLE ACUTE ACCENT) - 0x0304 (COMBINING MACRON) - 0x0132 (LATIN CAPITAL LIGATURE IJ) - 0x014A (LATIN CAPITAL LETTER ENG) - 0x1E9E (LATIN CAPITAL LETTER SHARP S) - 0x0133 (LATIN SMALL LIGATURE IJ) - 0x0237 (LATIN SMALL LETTER DOTLESS J) - 0x014B (LATIN SMALL LETTER ENG) - 0x00AA (FEMININE ORDINAL INDICATOR) - 0x0307 (COMBINING DOT ABOVE) - 0x0302 (COMBINING CIRCUMFLEX ACCENT) - 0x030C (COMBINING CARON) - 0x0306 (COMBINING BREVE) - 0x030A (COMBINING RING ABOVE) - 0x0303 (COMBINING TILDE) - 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.
⚠️ Ledger-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+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+2248 ALMOST EQUAL TO: 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
Or you can add the above codepoints to one of the subsets supported by the font:
menu
,cyrillic
,latin
,latin-ext
[code: unreachable-subsetting]
Check license file has good copyright string.
🔥 Ledger-Regular.ttf
- 🔥 FAIL
First line in license file is:
"copyright (c) 2012, 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.
⚠️ Ledger-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?
⚠️ Ledger-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]
Version format is correct in 'name' table?
🔥 Ledger-Regular.ttf
- 🔥 FAIL
The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "1.003" [code: bad-version-strings]
- 🔥 FAIL
The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "1.003" [code: bad-version-strings]
METADATA.pb subsets should be alphabetically ordered.
🔥 Ledger-Regular.ttf
- 🔥 FAIL
METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'cyrillic', 'latin', 'latin-ext'] and expected ['cyrillic', 'latin', 'latin-ext', 'menu'] [code: not-sorted]
METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?
🔥 Ledger-Regular.ttf
- 🔥 FAIL
METADATA.pb font full_name = "Ledger" does not match post_script_name = "Ledger-Regular" [code: mismatch]
Copyright notices match canonical pattern in METADATA.pb
🔥 Ledger-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." [code: bad-notice-format]
Copyright notices match canonical pattern in fonts
🔥 Ledger-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." [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." [code: bad-notice-format]
Check font names are correct
⚠️ Ledger-Regular.ttf
- ⚠️ WARN
Regular missing from full name [code: lacks-regular]
A static fonts directory with at least two fonts must accompany variable fonts
⚠️ Ledger-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.
⚠️ Ledger-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.
🔥 Ledger-Regular.ttf
- 🔥 FAIL
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/ledger/Ledger-Regular.ttf']. [code: missing-os2-fsselection-bit7]
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ Ledger-Regular.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
Ensure fonts do not contain any pre-production tables.
⚠️ Ledger-Regular.ttf
- ⚠️ WARN
This font file contains the following pre-production tables: FFTM [code: has-debugging-tables]
Section: Universal
🔥🔥⚠️⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩ℹ️ℹ️Font contains '.notdef' as its first glyph?
🔥 Ledger-Regular.ttf
- 🔥 FAIL
The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]
Are there unwanted tables?
🔥 Ledger-Regular.ttf
- 🔥 FAIL
The following unwanted font tables were found:
- FFTM - Table contains redundant FontForge timestamp info
They can be removed with the 'fix-unwanted-tables' script provided by gftools. [code: unwanted-tables]
Check font contains no unreachable glyphs
⚠️ Ledger-Regular.ttf
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- nonmarkingreturn
[code: unreachable-glyphs]
Check if each glyph has the recommended amount of contours.
⚠️ Ledger-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: uni0218 Contours detected: 1 Expected: 2 - Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: uni0218 Contours detected: 1 Expected: 2
[code: contour-count]
Does the font contain a soft hyphen?
⚠️ Ledger-Regular.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
Check math signs have the same width.
⚠️ Ledger-Regular.ttf
- ⚠️ WARN
The most common width is 618 among a set of 6 math glyphs. The following math glyphs have a different width, though:
Width = 611: plus, multiply, equal, minus
Width = 562: greater, logicalnot, less [code: width-outliers]
Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)
⚠️ Ledger-Regular.ttf
- ⚠️ 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
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.dsig
⚠️Does the font have a DSIG table?
⚠️ Ledger-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]