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 | 1 | 10 | 117 | 6 | 117 |
0% | 0% | 0% | 4% | 47% | 2% | 47% |
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: 0.12.10
OpenType Specification Checks
⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩Fonts have consistent underline thickness?
Fonts have consistent PANOSE family type?
Make sure all font files have the same version value.
Check that OS/2.fsSelection bold & italic settings are unique for each NameID1
Verify that each group of fonts with the same nameID 1 has maximum of 4 fonts.
Verify that family names in the name table are consistent across all fonts in the family. Checks Typographic Family name (nameID 16) if present, otherwise uses Font Family name (nameID 1)
CFF table FontName must match name table ID 6 (PostScript name).
Name table ID 6 (PostScript name) must be consistent across platforms.
Check name table for empty records.
Description strings in the name table must not contain copyright info.
Does full font name begin with the font family name?
The variable font 'wght' (Weight) axis coordinate must be 400 on the 'Regular' instance.
The variable font 'wdth' (Width) axis coordinate must be 100 on the 'Regular' instance.
The variable font 'slnt' (Slant) axis coordinate must be zero on the 'Regular' instance.
The variable font 'ital' (Italic) axis coordinate must be zero on the 'Regular' instance.
The variable font 'opsz' (Optical Size) axis coordinate should be between 10 and 16 on the 'Regular' instance.
The variable font 'slnt' (Slant) axis coordinate specifies positive values in its range?
The variable font 'ital' (Italic) axis coordinates is in a valid range?
The variable font 'wght' (Weight) axis coordinate must be within spec range of 1 to 1000 on all instances.
The variable font 'wdth' (Width) axis coordinate must strictly greater than zero.
All fvar axes have a correspondent Axis Record on STAT table?
Does the number of glyphs in the loca table match the maxp table?
EXPERIMENTAL CHECK - Since 2024/Jun/20
Does the font's CFF table top dict strings fit into the ASCII range?
Is the CFF subr/gsubr call depth > 10?
Does the font use deprecated CFF operators or operations?
Is the CFF2 subr/gsubr call depth > 10?
Checking font version fields (head and name table).
Font has correct post table version?
Checking correctness of monospaced metadata.
Check if OS/2 xAvgCharWidth is correct.
Check if OS/2 fsSelection matches head macStyle bold and italic bits.
Checking unitsPerEm value is reasonable.
Does the font have a DSIG table?
Check glyphs in mark glyph class are non-spacing.
Check mark characters are in GDEF mark glyph class.
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
The following mark characters could be in the GDEF mark glyph class: auMatra_chakma (U+1112F) and oMatra_chakma (U+1112E)
[code: mark-chars]
Check GDEF mark glyph class doesn't have characters that are not marks.
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
The following non-mark characters should not be in the GDEF mark glyph class: U+11145 and U+11146
[code: non-mark-chars]
Does GPOS table have kerning information? This check skips monospaced fonts as defined by post.isFixedPitch value
Is there a usable "kern" table declared in the font?
Is there any unused data at the end of the glyf table?
Font follows the family naming recommendations?
MaxAdvanceWidth is consistent with values in the Hmtx and Hhea tables?
PostScript name follows OpenType specification requirements?
Check for points out of bounds.
Check glyphs do not have duplicate components which have the same x,y coordinates.
Check code page character ranges
Does the font have any invalid feature tags?
Does the font have any invalid script tags?
Does the font have any invalid language tags?
Checking post.italicAngle value.
Checking head.macStyle value.
Checking OS/2 fsSelection value.
Check name table IDs 1, 2, 16, 17 to conform to Italic style.
Validates that the value of axisNameID used by each VariationAxisRecord is greater than 255 and less than 32768.
Validates that the value of subfamilyNameID used by each InstanceRecord is 2, 17, or greater than 255 and less than 32768.
Validates that the value of postScriptNameID used by each InstanceRecord is 6, 0xFFFF, or greater than 255 and less than 32768.
Validates that when an instance record is included for the default instance, its subfamilyNameID value is set to a name ID whose string is equal to the string of either name ID 2 or 17, and its postScriptNameID value is set to a name ID whose string is equal to the string of name ID 6.
Validates that all of the instance records in a given font have the same size.
Validates that all of the instance records in a given font have distinct data.
Validate foundry-defined design-variation axis tag names.
Check that family axis ranges are indentical
STAT table has Axis Value tables?
Checking OS/2 achVendID against configuration.
Check hhea.caretSlopeRise and hhea.caretSlopeRun
Ensure VFs have 'ital' STAT axis.
Ensure 'ital' STAT axis is boolean value
Ensure 'ital' STAT axis is last.
Universal Profile Checks
⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩⏩ℹ️Check accent of Lcaron, dcaron, lcaron, tcaron
Check that glyph for U+0675 ARABIC LETTER HIGH HAMZA is not a mark.
Check that Arabic spacing symbols U+FBB2–FBC1 aren't classified as marks.
Ensure the font supports case swapping for all its glyphs.
Does the font contain chws and vchw features?
Check if each glyph has the recommended amount of contours.
⚠️ NotoSansChakma-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:
[code: contour-count]- Glyph name: aogonek Contours detected: 3 Expected: 2 - Glyph name: uogonek Contours detected: 2 Expected: 1 - Glyph name: aogonek Contours detected: 3 Expected: 2 - Glyph name: uogonek Contours detected: 2 Expected: 1
Checking all files are in the same directory.
Each font in a family must have the same set of vertical metrics values.
Checking OS/2 usWinAscent & usWinDescent.
Do we have the latest version of FontBakery installed?
Ensure that the font can be rasterized by FreeType.
Ensure no GPOS7 lookups are present.
EXPERIMENTAL CHECK - Since 2024/Jun/10
Ensure 'smcp' (small caps) lookups are defined before ligature lookups in the 'GSUB' table.
Detect any interpolation issues in the font.
Check that legacy accents aren't used in composite glyphs.
Checking Vertical Metric Linegaps.
Font contains '.notdef' as its first glyph?
Check math signs have the same width.
Name table records must not have trailing spaces.
Checking OS/2 Metrics match hhea Metrics.
Checking with ots-sanitize.
Font contains all required tables?
Ensure indic fonts have the Indian Rupee Sign glyph.
Font has the proper sfntVersion value?
Does the font contain a soft hyphen?
Checking STAT table entries in static fonts.
Check correctness of STAT table strings
EXPERIMENTAL CHECK - Since 2024/Jun/04
Check tabular widths don't have kerning.
Ensure component transforms do not perform scaling or rotation.
Checking with fontTools.ttx
EXPERIMENTAL CHECK - Since 2024/Jul/17
Checking that the typoAscender exceeds the yMax of the /Agrave.
Font contains unique glyph names?
Check font contains no unreachable glyphs
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
[code: unreachable-glyphs]- ttaa.base - tthaa.base
Are there unwanted tables?
Glyph names are all valid?
Font has **proper** whitespace glyph names?
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
Glyph 0x00A0 is called "nbspace": Change to "uni00A0"
[code: not-recommended-00a0]
Font contains glyphs for whitespace characters?
Whitespace glyphs have ink?
Space and non-breaking space have the same width?
Article Checks
⚠️Validate size, and resolution of article images, and ensure article page has minimum length and includes visual assets.
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
Family metadata at fonts/NotoSansChakma/googlefonts/ttf does not have an article.
[code: lacks-article]
Metadata Checks
⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩Does METADATA.pb copyright field contain broken links?
METADATA.pb: Font styles are named canonically?
METADATA.pb: Check that font weight has a canonical value.
Check samples can be rendered.
Ensure METADATA.pb category field is valid.
Check if category on METADATA.pb matches what can be inferred from the family name.
Validate VF axes match the ones declared on METADATA.pb.
METADATA.pb: Check URL on copyright string is the same as in repository_url field.
METADATA.pb: Copyright notice is the same in all fonts?
EXPERIMENTAL CHECK - Since 2024/May/22
Validate 'date_added' field on METADATA.pb.
METADATA.pb: Designers are listed correctly on the Google Fonts catalog?
Multiple values in font designer field in METADATA.pb must be separated by commas.
At least one designer is declared in METADATA.pb
Ensure METADATA.pb does not use escaped strings.
Check font family directory name.
Check that METADATA.pb family values are all the same.
METADATA.pb: Font filenames match font.filename entries?
Validate METADATA.pb axes values are within gf_axisregistry bounds.
Validate METADATA.pb axes tags are defined in gf_axisregistry.
Ensure there is a regular style defined in METADATA.pb.
Check METADATA.pb includes production subsets.
Check METADATA.pb file only contains a single CJK subset.
METADATA.pb license is "APACHE2", "UFL" or "OFL"?
METADATA.pb font.filename and font.post_script_name fields have equivalent values?
METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?
METADATA.pb: Check font name is the same as family name.
METADATA.pb weight matches postScriptName for static fonts.
METADATA.pb should contain at least "menu" and "latin" subsets.
METADATA.pb: Validate family.minisite_url field.
METADATA.pb font.name and font.full_name fields match the values declared on the name table?
METADATA.pb font.name value should be same as the family name declared on the name table.
Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.
Check METADATA.pb font weights are correct.
Check METADATA.pb parse correctly.
METADATA.pb: Check for primary_script
METADATA.pb: Regular should be 400.
Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.
METADATA.pb subsets should be alphabetically ordered.
Ensure METADATA.pb lists all font binaries.
METADATA.pb: check if fonts field only has unique "full_name" values.
METADATA.pb: check if fonts field only contains unique style:weight pairs.
Check for codepoints not covered by METADATA subsets.
⚠️ NotoSansChakma-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, math, tifinagh, coptic
- U+0306 COMBINING BREVE: try adding one of: tifinagh, old-permic
- U+0307 COMBINING DOT ABOVE: try adding one of: canadian-aboriginal, coptic, todhri, tifinagh, malayalam, tai-le, old-permic, duployan, hebrew, math, syriac
- U+030A COMBINING RING ABOVE: try adding one of: syriac, duployan
- 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
- U+0327 COMBINING CEDILLA: try adding math
- U+0328 COMBINING OGONEK: not included in any glyphset definition
Or you can add the above codepoints to one of the subsets supported by the font:
[code: unreachable-subsetting]chakma
,latin
,latin-ext
Check for METADATA subsets with zero support.
METADATA.pb font.filename field contains font name in right format?
METADATA.pb font.full_name field contains font name in right format?
Check name ID 25 to end with "Italic" for Italic VFs.
METADATA.pb font.post_script_name field contains font name in right format?
Description Checks
🔥⏩⏩⏩⏩⏩⏩⏩⏩Does DESCRIPTION file contain broken links?
DESCRIPTION.en_us.html should end in a linebreak.
On a family update, the DESCRIPTION.en_us.html file should ideally also be updated.
Does DESCRIPTION file contain a upstream Git repo URL?
Check the description doesn't contain unsupported html elements
DESCRIPTION.en_us.html must have more than 200 bytes.
Check for presence of an ARTICLE.en_us.html file
🔥 NotoSansChakma-Regular.ttf
-
🔥 FAIL
This is a Noto font but it lacks an ARTICLE.en_us.html file.
[code: missing-article] -
🔥 FAIL
This is a Noto font but it lacks a DESCRIPTION.en_us.html file.
[code: missing-description]
URLs on DESCRIPTION file must not display http(s) prefix.
Is this a proper HTML snippet?
Shaping Checks
⚠️⏩⏩⏩Check that texts shape as per expectation
Check that no forbidden glyphs are found while shaping
Check that no collisions are found while shaping
Ensure dotted circle glyph is present and can attach marks.
Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
⚠️ NotoSansChakma-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: į̆ į̇ į̈ į̊ į̋ į̦̀ į̦́ į̦̂ į̦̃ į̦̄ į̦̆ į̦̇ į̦̈ į̦̊ į̦̋ į̦̌ į̧̀ į̧́ į̧̂ į̧̃
Your font fully covers the following languages that require the soft-dotted feature: Lithuanian (Latn, 2,357,094 speakers), Dutch (Latn, 31,709,104 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Dan (Latn, 1,099,244 speakers), Dii (Latn, 71,000 speakers), Mundani (Latn, 34,000 speakers), Ejagham (Latn, 120,000 speakers), Mfumte (Latn, 79,000 speakers), Ma’di (Latn, 584,000 speakers), Gulay (Latn, 250,478 speakers), Basaa (Latn, 332,940 speakers), Lugbara (Latn, 2,200,000 speakers), Bete-Bendi (Latn, 100,000 speakers), Cicipu (Latn, 44,000 speakers), Ekpeye (Latn, 226,000 speakers), Southern Kisi (Latn, 360,000 speakers), Koonzime (Latn, 40,000 speakers), Igbo (Latn, 27,823,640 speakers), Fur (Latn, 1,230,163 speakers), Nateni (Latn, 100,000 speakers), Yala (Latn, 200,000 speakers), Teke-Ebo (Latn, 260,000 speakers), Aghem (Latn, 38,843 speakers), Ijo, Southeast (Latn, 2,471,000 speakers), Kom (Latn, 360,685 speakers), Vute (Latn, 21,000 speakers), Bafut (Latn, 158,146 speakers), Mango (Latn, 77,000 speakers), Avokaya (Latn, 100,000 speakers), Han (Latn, 6 speakers), Ebira (Latn, 2,200,000 speakers), South Central Banda (Latn, 244,000 speakers), Heiltsuk (Latn, 300 speakers), Sar (Latn, 500,000 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Ngbaka (Latn, 1,020,000 speakers), Kaska (Latn, 125 speakers), Zapotec (Latn, 490,000 speakers), Navajo (Latn, 166,319 speakers), Kpelle, Guinea (Latn, 622,000 speakers), Belarusian (Cyrl, 10,064,517 speakers), Makaa (Latn, 221,000 speakers), Nzakara (Latn, 50,000 speakers).
[code: soft-dotted]
Outline Checks
⚠️Are there any misaligned on-curve points?
Are any segments inordinately short?
Do any segments have colinear vectors?
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
The following glyphs have colinear vectors:
[code: found-colinear-vectors]* naa_chakma (U+1111A): L<<497.0,418.0>--<501.0,418.0>> -> L<<501.0,418.0>--<506.0,418.0>> * saa_chakma (U+11125): L<<553.0,272.0>--<553.0,272.0>> -> L<<553.0,272.0>--<553.0,272.0>>
Do outlines contain any jaggy segments?
Do outlines contain any semi-vertical or semi-horizontal lines?
Check the direction of the outermost contour in each glyph
Font File Checks
⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️Are there unwanted Apple tables?
Checking file is named canonically.
Does the font contain less than 150 CJK characters?
Check font follows the Google Fonts CJK vertical metric schema
Check if the vertical metrics of a CJK family are similar to the same family hosted on Google Fonts.
Color layers should have a minimum brightness
Check font has the expected color font tables.
Put an empty glyph on GID 1 right after the .notdef glyph for COLRv0 fonts.
EPAR table present in font?
Ensure files are not too large.
Copyright notices match canonical pattern in fonts
Familyname must be unique according to namecheck.fontdata.com
Check font names are correct
Checking OS/2 fsType does not impose restrictions.
Check variable font instances
All name entries referenced by fvar instances exist on the name table?
Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?
Validate defaults on fvar table match registered fallback names in GFAxisRegistry.
Check glyphs do not have components which are themselves components.
Check Google Fonts glyph coverage.
Font has ttfautohint params?
Show hinting filesize impact.
PPEM must be an integer on hinted fonts.
Is there kerning info for non-ligated sequences?
Are there caret positions declared for every ligature?
Ensure variable fonts include an avar table.
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ NotoSansChakma-Regular.ttf
-
⚠️ WARN
This font file does not have a 'meta' table.
[code: lacks-meta-table]