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 | 5 | 20 | 60 | 8 | 148 |
0% | 3% | 11% | 34% | 4% | 83% |
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 broken links?
🔥 AkayaKanadaka-Regular.ttf
- 🔥 FAIL
The following links are broken in the DESCRIPTION file: /specimen/Akaya+Telivigala [code: broken-links]
DESCRIPTION.en_us.html should end in a linebreak.
⚠️ AkayaKanadaka-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.
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
OS/2 VendorID value 'NONE' 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.
🔥 AkayaKanadaka-Regular.ttf
- 🔥 FAIL
Missing required codepoints:
- 0x010A (LATIN CAPITAL LETTER C WITH DOT ABOVE) - 0x0120 (LATIN CAPITAL LETTER G WITH DOT ABOVE) - 0x0126 (LATIN CAPITAL LETTER H WITH STROKE) - 0x014A (LATIN CAPITAL LETTER ENG) - 0x1E9E (LATIN CAPITAL LETTER SHARP S) - 0x016C (LATIN CAPITAL LETTER U WITH BREVE) - 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) - 0x010B (LATIN SMALL LETTER C WITH DOT ABOVE) - 0x0121 (LATIN SMALL LETTER G WITH DOT ABOVE) - 0x0127 (LATIN SMALL LETTER H WITH STROKE) - 0x014B (LATIN SMALL LETTER ENG) - 0x016D (LATIN SMALL LETTER U WITH BREVE) - 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) - 0x0312 (COMBINING TURNED COMMA ABOVE)
[code: missing-codepoints]
Check for codepoints not covered by METADATA subsets.
⚠️ AkayaKanadaka-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, yi
- U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
- 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+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, malayalam, old-permic, tifinagh, syriac, math, tai-le
- U+030A COMBINING RING ABOVE: try adding 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+0325 COMBINING RING BELOW: try adding syriac
- U+0326 COMBINING COMMA BELOW: not included in any glyphset definition
- U+0327 COMBINING CEDILLA: not included in any glyphset definition
- U+0328 COMBINING OGONEK: not included in any glyphset definition
- U+03C0 GREEK SMALL LETTER PI: try adding one of: greek, math, yi
- U+200A HAIR SPACE: not included in any glyphset definition
- U+2021 DOUBLE DAGGER: try adding adlam
- U+2030 PER MILLE SIGN: try adding adlam
- U+2055 FLOWER PUNCTUATION MARK: try adding syloti-nagri
- U+2126 OHM SIGN: not included in any glyphset definition
- U+212E ESTIMATED SYMBOL: not included in any glyphset definition
- U+2202 PARTIAL DIFFERENTIAL: try adding math
- U+2206 INCREMENT: try adding math
- U+220F N-ARY PRODUCT: try adding math
- U+2211 N-ARY SUMMATION: try adding math
- U+2219 BULLET OPERATOR: try adding one of: symbols, math, tai-tham, yi
- U+221A SQUARE ROOT: try adding math
- U+221E INFINITY: try adding math
- U+222B INTEGRAL: try adding math
- U+2248 ALMOST EQUAL TO: try adding math
- U+2260 NOT EQUAL TO: try adding math
- U+2264 LESS-THAN OR EQUAL TO: try adding math
- U+2265 GREATER-THAN OR EQUAL TO: try adding math
- U+25CA LOZENGE: try adding one of: symbols, math
- 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:
kannada
,latin
,latin-ext
,menu
[code: unreachable-subsetting]
Check copyright namerecords match license file.
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ 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?
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ 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=3, enc=1, 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=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]
Font has old ttfautohint applied?
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
ttfautohint used in font = 1.8.3; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]
METADATA.pb: Check URL on copyright string is the same as in repository_url field.
🔥 AkayaKanadaka-Regular.ttf
- 🔥 FAIL
Value of repository_url field is
But font copyright string has: https://github.com/vaishnavimurthy/Akaya-Kanadaka [code: mismatch]
Are there caret positions declared for every ligature?
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]
Is there kerning info for non-ligated sequences?
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
GPOS table lacks kerning info for the following non-ligated sequences:
- f + i - i + l [code: lacks-kern-info]
A static fonts directory with at least two fonts must accompany variable fonts
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]
METADATA.pb: Designers are listed correctly on the Google Fonts catalog?
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
It seems that Juan Luis Blanco is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]
On a family update, the DESCRIPTION.en_us.html file should ideally also be updated.
⚠️ AkayaKanadaka-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]
Ensure Stylistic Sets have description.
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
Section: Universal
🔥⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩ℹ️ℹ️Check font contains no unreachable glyphs
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- knSHRII - uni00740CAF.below - uni0CA4.below.02 - uni0CB0.below.03 - uni0CB10CCD - uni0CDE0CCD
[code: unreachable-glyphs]
Check if each glyph has the recommended amount of contours.
⚠️ AkayaKanadaka-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: asterisk Contours detected: 5 Expected: 1 or 4 - Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: Racute Contours detected: 2 Expected: 3 - Glyph name: uni0156 Contours detected: 2 Expected: 3 - Glyph name: Rcaron Contours detected: 2 Expected: 3 - Glyph name: uni1E5A Contours detected: 2 Expected: 3 - Glyph name: uni1E5C Contours detected: 3 Expected: 4 - Glyph name: uni20B9 Contours detected: 2 Expected: 1 - Glyph name: Racute Contours detected: 2 Expected: 3 - Glyph name: Rcaron Contours detected: 2 Expected: 3 - Glyph name: asterisk Contours detected: 5 Expected: 1 or 4 - Glyph name: fi Contours detected: 1 Expected: 3 - Glyph name: fl Contours detected: 1 Expected: 2 - Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: uni0156 Contours detected: 2 Expected: 3 - Glyph name: uni1E5A Contours detected: 2 Expected: 3 - Glyph name: uni1E5C Contours detected: 3 Expected: 4 - Glyph name: uni20B9 Contours detected: 2 Expected: 1
[code: contour-count]
Does the font contain a soft hyphen?
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
Ensure component transforms do not perform scaling or rotation.
🔥 AkayaKanadaka-Regular.ttf
- 🔥 FAIL
The following glyphs had components with scaling or rotation or inverted outline direction:
- uni0123 (component uni0326) [code: transformed-components]
Section: fontbakery.profiles.dsig
⚠️Does the font have a DSIG table?
⚠️ AkayaKanadaka-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 glyphs in mark glyph class are non-spacing.
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
The following spacing glyphs may be in the GDEF mark glyph class by mistake: uni0C82 (U+0C82), uni0C83 (U+0C83), uni0CBE (U+0CBE), uni0CC0 (U+0CC0), uni0CC1 (U+0CC1), uni0CC1.tall (unencoded), uni0CC2 (U+0CC2), uni0CC3 (U+0CC3), uni0CC7 (U+0CC7), uni0CC8 (U+0CC8), uni0CCA (U+0CCA), uni0CCB (U+0CCB), uni0CCC (U+0CCC), uni0CCD (U+0CCD), uni0CD5 (U+0CD5) and uni0CD6 (U+0CD6) [code: spacing-mark-glyphs]
Check GDEF mark glyph class doesn't have characters that are not marks.
⚠️ AkayaKanadaka-Regular.ttf
- ⚠️ WARN
The following non-mark characters should not be in the GDEF mark glyph class: U+0C82, U+0C83, U+0CBE, U+0CC0, U+0CC1, U+0CC2, U+0CC3, U+0CC7, U+0CC8, U+0CCA, U+0CCB, U+0CD5 and U+0CD6 [code: non-mark-chars]
Section: Shaping Checks
🔥⚠️⏩⏩⏩Ensure dotted circle glyph is present and can attach marks.
🔥 AkayaKanadaka-Regular.ttf
- 🔥 FAIL
The following glyphs could not be attached to the dotted circle glyph:
- acutecomb - dotbelowcomb - gravecomb - tildecomb - uni0302 - uni0304 - uni0306 - uni0307 - uni0308 - uni030A - uni030B - uni030C - uni0325 - uni0326 - uni0327 - uni0328 - uni0CBC [code: unattached-dotted-circle-marks]
Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
⚠️ AkayaKanadaka-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: Igbo (Latn, 27,823,640 speakers), Ebira (Latn, 2,200,000 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Ejagham (Latn, 120,000 speakers), Dan (Latn, 1,099,244 speakers), Dutch (Latn, 31,709,104 speakers), Ma’di (Latn, 584,000 speakers), Belarusian (Cyrl, 10,064,517 speakers), Lithuanian (Latn, 2,357,094 speakers), Basaa (Latn, 332,940 speakers), Aghem (Latn, 38,843 speakers), Navajo (Latn, 166,319 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Avokaya (Latn, 100,000 speakers), Lugbara (Latn, 2,200,000 speakers), Kom (Latn, 360,685 speakers), Nateni (Latn, 100,000 speakers), Koonzime (Latn, 40,000 speakers). [code: soft-dotted]