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 | ☠ FATAL | 🔥 FAIL | ⚠️ WARN | ⏩ SKIP | ℹ️ INFO | ✅ PASS |
|---|---|---|---|---|---|---|
| 0 | 0 | 3 | 9 | 110 | 7 | 107 |
| 0% | 0% | 1% | 4% | 47% | 3% | 45% |
Meaning of check results:
- 💥 An ERROR is something wrong with FontBakery itself, possibly a bug.
- ☠ A FATAL is an extremely severe issue that must be addressed immediately.
- 🔥 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: 1.1.0
Universal Profile Checks
⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️Check accent of Lcaron, dcaron, lcaron, tcaron
Lcaron, dcaron, lcaron, tcaron should NOT be composed with quoteright or quotesingle or comma or caron(comb). It should be composed with a distinctive glyph which doesn't look like an apostrophe.
Source: https://ilovetypography.com/2009/01/24/on-diacritics/ http://diacritics.typo.cz/index.php?id=5 https://www.typotheque.com/articles/lcaron
- Original proposal: https://github.com/fonttools/fontbakery/issues/3308
⚠️ Ameridard-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] -
✅ PASS
Looks good!
Check if each glyph has the recommended amount of contours.
Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be constructured in a handful of ways. This means a glyph's contour count will only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3 contours, depending on whether its double story or single story.
However, a quotedbl should have 2 contours, unless the font belongs to a display family.
This check currently does not cover variable fonts because there's plenty of alternative ways of constructing glyphs with multiple outlines for each feature in a VarFont. The expected contour count data for this check is currently optimized for the typical construction of glyphs in static fonts.
- Original proposal: https://github.com/fonttools/fontbakery/issues/4829
⚠️ Ameridard-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: at Contours detected: 4 Expected: 2 - Glyph name: AE Contours detected: 3 Expected: 2 - Glyph name: ae Contours detected: 4 Expected: 3 - Glyph name: eogonek Contours detected: 3 Expected: 2 - Glyph name: tcaron Contours detected: 1 Expected: 2 - Glyph name: Uogonek Contours detected: 2 Expected: 1 - Glyph name: uni25CC Contours detected: 8 Expected: 16 or 12 - Glyph name: AE Contours detected: 3 Expected: 2 - Glyph name: Uogonek Contours detected: 2 Expected: 1 - Glyph name: ae Contours detected: 4 Expected: 3 - 4 more.Use -F or --full-lists to disable shortening of long lists.
[code: contour-count]
Article Checks
⚠️Validate size, and resolution of article images, and ensure article page has minimum length and includes visual assets.
The purpose of this check is to ensure images (either raster or vector files) are not excessively large in filesize and resolution.
These constraints are loosely based on infrastructure limitations under default configurations.
It also ensures that the article page has a minimum length and includes at least one visual asset.
- Original proposal: https://github.com/fonttools/fontbakery/issues/4594
⚠️ Ameridard-Regular.ttf
-
⚠️ WARN
Family metadata at remix/salida does not have an article.
[code: lacks-article]
Metadata Checks
⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩Check for codepoints not covered by METADATA subsets.
This check ensures that all encoded glyphs in the font are covered by a subset declared in the METADATA.pb. Google Fonts splits the font into a set of subset fonts based on the contents of the subsets field and the subset definitions in the glyphsets repository.
Any encoded glyphs which are not by any of these subset definitions will not be served in the subsetted fonts, and so will be unreachable to the end user.
- Original proposal: https://github.com/fonttools/fontbakery/issues/4097
- See also: https://github.com/fonttools/fontbakery/pull/4273
⚠️ Ameridard-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+02D8 BREVE: try adding one of: yi, canadian-aboriginal
- U+02D9 DOT ABOVE: try adding one of: yi, canadian-aboriginal
- U+02DB OGONEK: try adding one of: yi, canadian-aboriginal
- U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: cherokee, tifinagh, coptic, math
- U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh
- U+0307 COMBINING DOT ABOVE: try adding one of: duployan, todhri, malayalam, math, old-permic, syriac, coptic, tai-le, hebrew, canadian-aboriginal, tifinagh
- U+030A COMBINING RING ABOVE: try adding one of: duployan, syriac
- U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: cherokee, osage
- U+030C COMBINING CARON: try adding one of: cherokee, tai-le
- U+0326 COMBINING COMMA BELOW: try adding math 32 more.
Use -F or --full-lists to disable shortening of long lists.
Or you can add the above codepoints to one of the subsets supported by the font:
[code: unreachable-subsetting]latin,latin-ext
Glyphset Checks
🔥Shapes languages in all GF glyphsets.
This check uses a heuristic to determine which GF glyphsets a font supports. Then it checks the font for correct shaping behaviour for all languages in those glyphsets.
- Original proposal: https://github.com/googlefonts/fontbakery/issues/4147
🔥 Ameridard-Regular.ttf
-
🔥 FAIL
GF_TransLatin_Arabic glyphset:
[code: failed-language-shaping]FAIL messages Languages Mandatory orthography codepoints: The following base characters are missing from the font: ẞ de_Latn (German) -
⚠️ WARN
GF_TransLatin_Arabic glyphset:
[code: warning-language-shaping]WARN messages Languages Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ĕ The following auxiliary characters are missing from the font: Ĭ The following auxiliary characters are missing from the font: Ŀ The following auxiliary characters are missing from the font: Ŏ The following auxiliary characters are missing from the font: Ŭ The following auxiliary characters are missing from the font: ĕ The following auxiliary characters are missing from the font: ĭ The following auxiliary characters are missing from the font: ŀ The following auxiliary characters are missing from the font: ŏ The following auxiliary characters are missing from the font: ŭ ca_Latn (Catalan) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ĕ The following auxiliary characters are missing from the font: Ĭ The following auxiliary characters are missing from the font: Ŏ The following auxiliary characters are missing from the font: Ŭ The following auxiliary characters are missing from the font: ĕ The following auxiliary characters are missing from the font: ĭ The following auxiliary characters are missing from the font: ŏ The following auxiliary characters are missing from the font: ŭ cs_Latn (Czech), cy_Latn (Welsh), es_Latn (Spanish), hu_Latn (Hungarian), pt_Latn (Portuguese) and sk_Latn (Slovak) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ǿ The following auxiliary characters are missing from the font: ǿ da_Latn (Danish) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ĕ The following auxiliary characters are missing from the font: Ĭ The following auxiliary characters are missing from the font: Ŏ The following auxiliary characters are missing from the font: Ŭ The following auxiliary characters are missing from the font: ĕ The following auxiliary characters are missing from the font: ĭ The following auxiliary characters are missing from the font: ŏ The following auxiliary characters are missing from the font: ſ The following auxiliary characters are missing from the font: ŭ de_Latn (German) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ĕ The following auxiliary characters are missing from the font: Ĭ The following auxiliary characters are missing from the font: Ŏ The following auxiliary characters are missing from the font: Ŭ The following auxiliary characters are missing from the font: ĕ The following auxiliary characters are missing from the font: ĭ The following auxiliary characters are missing from the font: ŏ The following auxiliary characters are missing from the font: ŭ The following auxiliary characters are missing from the font: ʻ en_Latn (English) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ǧ The following auxiliary characters are missing from the font: Ǥ The following auxiliary characters are missing from the font: Ȟ The following auxiliary characters are missing from the font: Ǩ The following auxiliary characters are missing from the font: Ŝ The following auxiliary characters are missing from the font: ẞ The following auxiliary characters are missing from the font: Ʒ The following auxiliary characters are missing from the font: Ǯ The following auxiliary characters are missing from the font: ǧ The following auxiliary characters are missing from the font: ǥ The following auxiliary characters are missing from the font: ȟ The following auxiliary characters are missing from the font: ǩ The following auxiliary characters are missing from the font: ŝ The following auxiliary characters are missing from the font: ʒ The following auxiliary characters are missing from the font: ǯ fi_Latn (Finnish) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: ẞ The following auxiliary characters are missing from the font: Ǔ The following auxiliary characters are missing from the font: ſ The following auxiliary characters are missing from the font: ǔ fr_Latn (French) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: ẞ it_Latn (Italian) and pl_Latn (Polish) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ẽ The following auxiliary characters are missing from the font: Ĩ The following auxiliary characters are missing from the font: Ũ The following auxiliary characters are missing from the font: ẽ The following auxiliary characters are missing from the font: ĩ The following auxiliary characters are missing from the font: ũ Shaper didn't attach acutecomb to Aogonek when shaping the text 'Ą́' Shaper didn't attach tildecomb to Aogonek when shaping the text 'Ą̃' Shaper didn't attach acutecomb to Eogonek when shaping the text 'Ę́' Shaper didn't attach tildecomb to Eogonek when shaping the text 'Ę̃' Shaper didn't attach acutecomb to Edotaccent when shaping the text 'Ė́' Shaper didn't attach tildecomb to Edotaccent when shaping the text 'Ė̃' Shaper didn't attach acutecomb to Idotaccent when shaping the text 'İ́' Shaper didn't attach acutecomb to Idotaccent when shaping the text 'İ́' Shaper didn't attach gravecomb to Idotaccent when shaping the text 'İ̀' Shaper didn't attach gravecomb to Idotaccent when shaping the text 'İ̀' Shaper didn't attach tildecomb to Idotaccent when shaping the text 'İ̃' Shaper didn't attach tildecomb to Idotaccent when shaping the text 'İ̃' Shaper didn't attach acutecomb to Iogonek when shaping the text 'Į́' Shaper didn't attach uni0307 to Iogonek when shaping the text 'Į̇́' Shaper didn't attach acutecomb to uni0307 when shaping the text 'Į̇́' Shaper didn't attach tildecomb to Iogonek when shaping the text 'Į̃' Shaper didn't attach uni0307 to Iogonek when shaping the text 'Į̇̃' Shaper didn't attach tildecomb to uni0307 when shaping the text 'Į̇̃' Shaper didn't attach acutecomb to Uogonek when shaping the text 'Ų́' Shaper didn't attach tildecomb to Uogonek when shaping the text 'Ų̃' Shaper didn't attach acutecomb to Umacron when shaping the text 'Ū́' Shaper didn't attach tildecomb to Umacron when shaping the text 'Ū̃' Shaper didn't attach acutecomb to aogonek when shaping the text 'ą́' Shaper didn't attach tildecomb to aogonek when shaping the text 'ą̃' Shaper didn't attach acutecomb to eogonek when shaping the text 'ę́' Shaper didn't attach tildecomb to eogonek when shaping the text 'ę̃' Shaper didn't attach acutecomb to edotaccent when shaping the text 'ė́' Shaper didn't attach tildecomb to edotaccent when shaping the text 'ė̃' Shaper didn't attach acutecomb to iogonek when shaping the text 'į́' Shaper didn't attach uni0307 to iogonek when shaping the text 'į̇́' Shaper didn't attach acutecomb to uni0307 when shaping the text 'į̇́' Shaper didn't attach tildecomb to iogonek when shaping the text 'į̃' Shaper didn't attach uni0307 to iogonek when shaping the text 'į̇̃' Shaper didn't attach tildecomb to uni0307 when shaping the text 'į̇̃' Shaper didn't attach acutecomb to uogonek when shaping the text 'ų́' Shaper didn't attach tildecomb to uogonek when shaping the text 'ų̃' Shaper didn't attach acutecomb to umacron when shaping the text 'ū́' Shaper didn't attach tildecomb to umacron when shaping the text 'ū̃' lt_Latn (Lithuanian) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ǎ The following auxiliary characters are missing from the font: ǎ nb_Latn (Norwegian Bokmål) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: IJ The following auxiliary characters are missing from the font: ij nl_Latn (Dutch) Auxiliary orthography codepoints: The following auxiliary characters are missing from the font: Ĕ The following auxiliary characters are missing from the font: Ĭ The following auxiliary characters are missing from the font: Ŏ The following auxiliary characters are missing from the font: ẞ The following auxiliary characters are missing from the font: Ŭ The following auxiliary characters are missing from the font: ĕ The following auxiliary characters are missing from the font: ĭ The following auxiliary characters are missing from the font: ŏ The following auxiliary characters are missing from the font: ŭ tr_Latn (Turkish)
Shaping Checks
⚠️⏩⏩⏩Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
An accent placed on characters with a "soft dot", like i or j, causes the dot to disappear. An explicit dot above can be added where required. See "Diacritics on i and j" in Section 7.1, "Latin" in The Unicode Standard.
Characters with the Soft_Dotted property are listed in https://www.unicode.org/Public/UCD/latest/ucd/PropList.txt
See also: https://googlefonts.github.io/gf-guide/diacritics.html#soft-dotted-glyphs
- Original proposal: https://github.com/fonttools/fontbakery/issues/4059
⚠️ Ameridard-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̦̋ ǐ̦ ĩ̧ ĭ̧ i̧̇ i̧̊ i̧̋ ǐ̧ j̦̀ j̦́ ĵ̦ j̦̃ j̦̄ j̦̆ j̦̇ j̦̈
[code: soft-dotted]
Outline Checks
⚠️⚠️Are there any misaligned on-curve points?
This check heuristically looks for on-curve points which are close to, but do not sit on, significant boundary coordinates. For example, a point which has a Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the baseline, here we also check for points near the x-height (but only for lowercase Latin letters), cap-height, ascender and descender Y coordinates.
Not all such misaligned curve points are a mistake, and sometimes the design may call for points in locations near the boundaries. As this check is liable to generate significant numbers of false positives, it will pass if there are more than 100 reported misalignments.
- Original proposal: https://github.com/fonttools/fontbakery/pull/3088
⚠️ Ameridard-Regular.ttf
-
⚠️ WARN
The following glyphs have on-curve points which have potentially incorrect y coordinates:
* G (U+0047): X=656.0,Y=-2.0 (should be at baseline 0?) * G (U+0047): X=581.0,Y=-2.0 (should be at baseline 0?) * J (U+004A): X=14.0,Y=-2.0 (should be at baseline 0?) * J (U+004A): X=178.0,Y=-1.0 (should be at baseline 0?) * R (U+0052): X=481.0,Y=1.0 (should be at baseline 0?) * S (U+0053): X=194.0,Y=708.5 (should be at cap-height 708?) * S (U+0053): X=191.0,Y=-0.5 (should be at baseline 0?) * a (U+0061): X=497.0,Y=1.0 (should be at baseline 0?) * k (U+006B): X=377.0,Y=506.0 (should be at x-height 508?) * k (U+006B): X=501.0,Y=506.0 (should be at x-height 508?) * 60 more.Use -F or --full-lists to disable shortening of long lists.
[code: found-misalignments]
Do outlines contain any jaggy segments?
This check heuristically detects outline segments which form a particularly small angle, indicative of an outline error. This may cause false positives in cases such as extreme ink traps, so should be regarded as advisory and backed up by manual inspection.
- Original proposal: https://github.com/fonttools/fontbakery/issues/3064
⚠️ Ameridard-Regular.ttf
-
⚠️ WARN
The following glyphs have jaggy segments:
[code: found-jaggy-segments]* tcaron (U+0165): B<<333.5,511.5>-<327.0,510.0>-<319.0,508.0>>/L<<319.0,508.0>--<331.0,508.0>> = 14.036243467926484
Font File Checks
🔥🔥⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️Check Google Fonts glyph coverage.
Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the GF-latin-core glyph-set.
- Original proposal: https://github.com/fonttools/fontbakery/pull/2488
🔥 Ameridard-Regular.ttf
-
🔥 FAIL
Missing required codepoints:
[code: missing-codepoints]- 0x1E9E (LATIN CAPITAL LETTER SHARP S)
Ensure fonts have ScriptLangTags declared on the 'meta' table.
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with just two DataMap records:
-
dlng: comma-separated ScriptLangTags that indicate which scripts, or languages and scripts, with possible variants, the font is designed for.
-
slng: comma-separated ScriptLangTags that indicate which scripts, or languages and scripts, with possible variants, the font supports.
The slng structure is intended to describe which languages and scripts the font overall supports. For example, a Traditional Chinese font that also contains Latin characters, can indicate Hant,Latn, showing that it supports Hant, the Traditional Chinese variant of the Hani script, and it also supports the Latn script.
The dlng structure is far more interesting. A font may contain various glyphs, but only a particular subset of the glyphs may be truly "leading" in the design, while other glyphs may have been included for technical reasons. Such a Traditional Chinese font could only list Hant there, showing that it’s designed for Traditional Chinese, but the font would omit Latn, because the developers don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and script. For example, if a font has Bulgarian Cyrillic alternates in the locl feature for the cyrl BGR OT languagesystem, it could also indicate in dlng explicitly that it supports bul-Cyrl. (Note that the scripts and languages in meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng structures.
All families in the Google Fonts collection should contain the 'meta' table. Windows 10 already uses it when deciding on which fonts to fall back to. The Google Fonts API and also other environments could use the data for smarter filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files already. But the meta table provides a convenient way to store this inside the font file, so some tools may add the data, and unrelated tools may read this data. This makes the solution much more portable and universal.
- Original proposal: https://github.com/fonttools/fontbakery/issues/3349
⚠️ Ameridard-Regular.ttf
-
⚠️ WARN
This font file does not have a 'meta' table.
[code: lacks-meta-table]
Version format is correct in 'name' table?
For Google Fonts, the version string must be in the format "Version X.Y". The version number must be greater than or equal to 1.000. (Additional information following the numeric version number is acceptable.) The "Version " prefix is a recommendation given by the OpenType spec.
- Original proposal: https://github.com/fonttools/fontbakery/issues/4829
🔥 Ameridard-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. The "Version " prefix is a recommendation given by the OpenType spec. Current version string is: "Version 0.300"
[code: bad-version-strings]
Checking OS/2 achVendID.
Microsoft keeps a list of font vendors and their respective contact info. This list is updated regularly and is indexed by a 4-char "Vendor ID" which is stored in the achVendID field of the OS/2 table.
Registering your ID is not mandatory, but it is a good practice since some applications may display the type designer / type foundry contact info on some dialog and also because that info will be visible on Microsoft's website:
https://docs.microsoft.com/en-us/typography/vendors/
This check verifies whether or not a given font's vendor ID is registered in that list or if it has some of the default values used by the most common font editors.
Each new FontBakery release includes a cached copy of that list of vendor IDs. If you registered recently, you're safe to ignore warnings emitted by this check, since your ID will soon be included in one of our upcoming releases.
- Original proposal: https://github.com/fonttools/fontbakery/issues/3943
- See also: https://github.com/fonttools/fontbakery/issues/4829
⚠️ Ameridard-Regular.ttf
-
⚠️ WARN
OS/2 VendorID value 'SOPA' 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]