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 | 14 | 15 | 63 | 8 | 141 |
0% | 8% | 8% | 34% | 4% | 76% |
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
🔥🔥🔥🔥🔥🔥🔥🔥⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️DESCRIPTION.en_us.html should end in a linebreak.
⚠️ Kavivanar-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.
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
OS/2 VendorID value ' ' 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.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
Missing required codepoints:
- 0x2026 (HORIZONTAL ELLIPSIS) - 0x0308 (COMBINING DIAERESIS) - 0x0300 (COMBINING GRAVE ACCENT) - 0x0301 (COMBINING ACUTE ACCENT) - 0x030B (COMBINING DOUBLE ACUTE ACCENT) - 0x0304 (COMBINING MACRON) - 0x0116 (LATIN CAPITAL LETTER E WITH DOT ABOVE) - 0x014A (LATIN CAPITAL LETTER ENG) - 0x1E9E (LATIN CAPITAL LETTER SHARP S) - 0x1E82 (LATIN CAPITAL LETTER W WITH ACUTE) - 0x0174 (LATIN CAPITAL LETTER W WITH CIRCUMFLEX) - 0x1E84 (LATIN CAPITAL LETTER W WITH DIAERESIS) - 0x1E80 (LATIN CAPITAL LETTER W WITH GRAVE) - 0x0176 (LATIN CAPITAL LETTER Y WITH CIRCUMFLEX) - 0x1EF2 (LATIN CAPITAL LETTER Y WITH GRAVE) - 0x0117 (LATIN SMALL LETTER E WITH DOT ABOVE) - 0x014B (LATIN SMALL LETTER ENG) - 0x1E83 (LATIN SMALL LETTER W WITH ACUTE) - 0x0175 (LATIN SMALL LETTER W WITH CIRCUMFLEX) - 0x1E85 (LATIN SMALL LETTER W WITH DIAERESIS) - 0x1E81 (LATIN SMALL LETTER W WITH GRAVE) - 0x0177 (LATIN SMALL LETTER Y WITH CIRCUMFLEX) - 0x1EF3 (LATIN SMALL LETTER Y WITH GRAVE) - 0x2022 (BULLET) - 0x0302 (COMBINING CIRCUMFLEX ACCENT) - 0x030C (COMBINING CARON) - 0x0306 (COMBINING BREVE) - 0x030A (COMBINING RING ABOVE) - 0x0303 (COMBINING TILDE) - 0x0312 (COMBINING TURNED COMMA ABOVE) - 0x0327 (COMBINING CEDILLA) - 0x0328 (COMBINING OGONEK)
[code: missing-codepoints]
Check for codepoints not covered by METADATA subsets.
⚠️ Kavivanar-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: canadian-aboriginal, yi, tifinagh
- U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
- U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi
- U+02DB OGONEK: try adding one of: canadian-aboriginal, yi
- U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
- U+0307 COMBINING DOT ABOVE: try adding one of: canadian-aboriginal, tai-le, old-permic, math, syriac, tifinagh, malayalam, coptic
- U+030F COMBINING DOUBLE GRAVE ACCENT: not included in any glyphset definition
- U+0311 COMBINING INVERTED BREVE: try adding coptic
- U+0326 COMBINING COMMA BELOW: not included in any glyphset definition
- U+03BC GREEK SMALL LETTER MU: try adding one of: math, greek
- U+FB01 LATIN SMALL LIGATURE FI: not included in any glyphset definition
- U+FB02 LATIN SMALL LIGATURE FL: not included in any glyphset definition
Or you can add the above codepoints to one of the subsets supported by the font:
latin
,latin-ext
,menu
,tamil
[code: unreachable-subsetting]
Check license file has good copyright string.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
First line in license file is:
"copyright (c) 2015, tharique azeez (http://thariqueazeez.com|zeezat@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.
⚠️ Kavivanar-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?
⚠️ Kavivanar-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]
Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]
Copyright notices match canonical pattern in METADATA.pb
🔥 Kavivanar-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) 2015, tharique azeez (http://thariqueazeez.com|zeezat@gmail.com)" [code: bad-notice-format]
Copyright notices match canonical pattern in fonts
🔥 Kavivanar-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) 2015, Tharique Azeez (http://thariqueazeez.com|zeezat@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) 2015, Tharique Azeez (http://thariqueazeez.com|zeezat@gmail.com)" [code: bad-notice-format]
METADATA.pb: Check URL on copyright string is the same as in repository_url field.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
Value of repository_url field is
But font copyright string has: http://thariqueazeez.com|zeezat@gmail.com [code: mismatch]
Check glyphs do not have components which are themselves components.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
The following glyphs have components which themselves are component glyphs: * uni01C4 and uni01C5 [code: found-nested-components]
Font enables smart dropout control in "prep" table instructions?
🔥 Kavivanar-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
⚠️ Kavivanar-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.
⚠️ Kavivanar-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.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/home/runner/work/gf-dashboard/gf-dashboard/fonts/ofl/kavivanar/Kavivanar-Regular.ttf']. [code: missing-os2-fsselection-bit7]
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
Section: Universal
🔥🔥🔥⚠️⚠️⚠️⏩⏩⏩⏩⏩ℹ️ℹ️Ensure indic fonts have the Indian Rupee Sign glyph.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
Please add a glyph for Indian Rupee Sign (₹) at codepoint U+20B9. [code: missing-rupee]
Check font contains no unreachable glyphs
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- NULL - uni000D
[code: unreachable-glyphs]
Check if each glyph has the recommended amount of contours.
⚠️ Kavivanar-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: currency Contours detected: 6 Expected: 2 - Glyph name: yen Contours detected: 3 Expected: 1 or 2 - Glyph name: registered Contours detected: 5 Expected: 3 or 4 - Glyph name: Eth Contours detected: 3 Expected: 2 - Glyph name: aogonek Contours detected: 3 Expected: 2 - Glyph name: Dcroat Contours detected: 3 Expected: 2 - Glyph name: dcroat Contours detected: 3 Expected: 2 - Glyph name: eogonek Contours detected: 3 Expected: 2 - Glyph name: hbar Contours detected: 2 Expected: 1 - Glyph name: lslash Contours detected: 2 Expected: 1 - Glyph name: OE Contours detected: 3 Expected: 2 - Glyph name: oe Contours detected: 6 Expected: 3 - Glyph name: Uogonek Contours detected: 2 Expected: 1 - Glyph name: uogonek Contours detected: 2 Expected: 1 - Glyph name: uni25CC Contours detected: 4 Expected: 16 or 12 - Glyph name: Dcroat Contours detected: 3 Expected: 2 - Glyph name: Eth Contours detected: 3 Expected: 2 - Glyph name: OE Contours detected: 3 Expected: 2 - Glyph name: Uogonek Contours detected: 2 Expected: 1 - Glyph name: aogonek Contours detected: 3 Expected: 2 - Glyph name: currency Contours detected: 6 Expected: 2 - Glyph name: dcroat Contours detected: 3 Expected: 2 - Glyph name: eogonek Contours detected: 3 Expected: 2 - Glyph name: fi Contours detected: 2 Expected: 3 - Glyph name: hbar Contours detected: 2 Expected: 1 - Glyph name: lslash Contours detected: 2 Expected: 1 - Glyph name: oe Contours detected: 6 Expected: 3 - Glyph name: registered Contours detected: 5 Expected: 3 or 4 - Glyph name: uni25CC Contours detected: 4 Expected: 16 or 12 - Glyph name: uogonek Contours detected: 2 Expected: 1 - Glyph name: yen Contours detected: 3 Expected: 1 or 2
[code: contour-count]
Space and non-breaking space have the same width?
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
Space and non-breaking space have differing width: The space glyph named space is 209 font units wide, non-breaking space named (uni00A0) is 230 font units wide, and both should be positive and the same. GlyphsApp has "Sidebearing arithmetic" (https://glyphsapp.com/tutorials/spacing) which allows you to set the non-breaking space width to always equal the space width. [code: different-widths]
Check math signs have the same width.
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
The most common width is 475 among a set of 3 math glyphs. The following math glyphs have a different width, though:
Width = 399: plusminus, plus
Width = 517: less
Width = 380: equal
Width = 487: greater
Width = 340: multiply [code: width-outliers]
Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
dcaron uses component comma. [code: bad-mark]
- 🔥 FAIL
Lcaron uses component comma. [code: bad-mark]
- 🔥 FAIL
lcaron uses component comma. [code: bad-mark]
- 🔥 FAIL
tcaron uses component comma. [code: bad-mark]
Section: fontbakery.profiles.head
🔥⏩Checking font version fields (head and name table).
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
head version is "1.88100" while name version string (for platform 1, encoding 0) is "Version 1.88". [code: mismatch]
- 🔥 FAIL
head version is "1.88100" while name version string (for platform 3, encoding 1) is "Version 1.88". [code: mismatch]
Section: fontbakery.profiles.dsig
⚠️Does the font have a DSIG table?
⚠️ Kavivanar-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: fontbakery.profiles.gdef
⚠️Check mark characters are in GDEF mark glyph class.
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
The following mark characters could be in the GDEF mark glyph class: uni0307 (U+0307), uni030F (U+030F), uni0311 (U+0311) and uni0326 (U+0326) [code: mark-chars]
Section: fontbakery.profiles.glyf
🔥Check glyphs do not have duplicate components which have the same x,y coordinates.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
The following glyphs have duplicate components which have the same x,y coordinates: * {'glyph': 'oe', 'component': 'o', 'x': 0, 'y': 0} [code: found-duplicates]
Section: Shaping Checks
🔥⚠️⏩⏩⏩Ensure dotted circle glyph is present and can attach marks.
🔥 Kavivanar-Regular.ttf
- 🔥 FAIL
The following glyphs could not be attached to the dotted circle glyph:
- tm_Anusvara - tm_Virama - tm_VowelIi [code: unattached-dotted-circle-marks]
Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
⚠️ Kavivanar-Regular.ttf
- ⚠️ WARN
The dot of soft dotted characters used in orthographies must disappear in the following strings: j̑
The dot of soft dotted characters should disappear in other cases, for example: i̇ i̦̇ j̇ j̏ j̦̇ j̦̏ j̦̑ į̇ į̏ į̑ į̦̇ į̦̏ į̦̑
Your font does not cover the following languages that require the soft-dotted feature: Dan (Latn, 1,099,244 speakers), Aghem (Latn, 38,843 speakers), Ebira (Latn, 2,200,000 speakers), Koonzime (Latn, 40,000 speakers), Nateni (Latn, 100,000 speakers), Igbo (Latn, 27,823,640 speakers), Basaa (Latn, 332,940 speakers), Ejagham (Latn, 120,000 speakers), Dutch (Latn, 31,709,104 speakers), Lithuanian (Latn, 2,357,094 speakers), Ma’di (Latn, 584,000 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Lugbara (Latn, 2,200,000 speakers), Kom (Latn, 360,685 speakers), Belarusian (Cyrl, 10,064,517 speakers), Navajo (Latn, 166,319 speakers), Avokaya (Latn, 100,000 speakers). [code: soft-dotted]