Fontbakery Technical Report

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 9 15 63 9 145
0% 5% 8% 33% 5% 76%

Note: The following loglevels were omitted in this report: SKIP, INFO, PASS, DEBUG

Meaning of check results:

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.

Check ID: <FontBakeryCheck:com.google.fonts/check/description/eof_linebreak>
⚠️ CutiveMono-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.

Check ID: <FontBakeryCheck:com.google.fonts/check/vendor_id>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    OS/2 VendorID value 'newt' 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.

Check ID: <FontBakeryCheck:com.google.fonts/check/glyph_coverage>
🔥 CutiveMono-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)
    
    
    - 0x1E9E (LATIN CAPITAL LETTER SHARP S)
    
    
    - 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.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/unreachable_subsetting>
⚠️ CutiveMono-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+0091 : not included in any glyphset definition
    • U+0092 : not included in any glyphset definition
    • U+0093 : not included in any glyphset definition
    • U+0094 : not included in any glyphset definition
    • U+009A : not included in any glyphset definition
    • U+009B : not included in any glyphset definition
    • U+009D : not included in any glyphset definition
    • U+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh
    • 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+0307 COMBINING DOT ABOVE: try adding one of: canadian-aboriginal, tifinagh, coptic, tai-le, malayalam
    • 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 greek
    • 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+220F N-ARY PRODUCT: not included in any glyphset definition
    • U+221E INFINITY: not included in any glyphset definition
    • U+222B INTEGRAL: 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+FB00 LATIN SMALL LIGATURE FF: not included in any glyphset definition
    • U+FB01 LATIN SMALL LIGATURE FI: not included in any glyphset definition
    • U+FB02 LATIN SMALL LIGATURE FL: not included in any glyphset definition
    • U+FB03 LATIN SMALL LIGATURE FFI: not included in any glyphset definition
    • U+FB04 LATIN SMALL LIGATURE FFL: 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 [code: unreachable-subsetting]

Check license file has good copyright string.

Check ID: <FontBakeryCheck:com.google.fonts/check/license/OFL_copyright>
🔥 CutiveMono-Regular.ttf
  • 🔥 FAIL

    First line in license file is:

    "copyright 2012 the cutive project authors (vern@newtypography.co.uk)"

    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.

Check ID: <FontBakeryCheck:com.google.fonts/check/name/license>
⚠️ CutiveMono-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?

Check ID: <FontBakeryCheck:com.google.fonts/check/name/license_url>
⚠️ CutiveMono-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]

Copyright notices match canonical pattern in METADATA.pb

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>
🔥 CutiveMono-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 2012 the cutive project authors (vern@newtypography.co.uk)" [code: bad-notice-format]

Copyright notices match canonical pattern in fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/font_copyright>
🔥 CutiveMono-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 2012 The Cutive Project Authors (vern@newtypography.co.uk)" [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 2012 The Cutive Project Authors (vern@newtypography.co.uk)" [code: bad-notice-format]

PPEM must be an integer on hinted fonts.

Check ID: <FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>
🔥 CutiveMono-Regular.ttf
  • 🔥 FAIL

    This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into an integer value.

    This can be accomplished by using the 'gftools fix-hinting' command:

    # create virtualenv
    python3 -m venv venv
    # activate virtualenv
    source venv/bin/activate
    # install gftools
    pip install git+https://www.github.com/googlefonts/tools
    

    [code: bad-flags]

A static fonts directory with at least two fonts must accompany variable fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/repo/vf_has_static_fonts>
⚠️ CutiveMono-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.

Check ID: <FontBakeryCheck:com.google.fonts/check/description/family_update>
⚠️ CutiveMono-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.

Check ID: <FontBakeryCheck:com.google.fonts/check/os2/use_typo_metrics>
🔥 CutiveMono-Regular.ttf
  • 🔥 FAIL

    OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/cutivemono/CutiveMono-Regular.ttf']. [code: missing-os2-fsselection-bit7]

Ensure fonts have ScriptLangTags declared on the 'meta' table.

Check ID: <FontBakeryCheck:com.google.fonts/check/meta/script_lang_tags>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    This font file does not have a 'meta' table. [code: lacks-meta-table]

Section: Universal

🔥🔥⚠️⚠️⏩⏩⏩⏩⏩⏩ℹ️ℹ️

Check font contains no unreachable glyphs

Check ID: <FontBakeryCheck:com.google.fonts/check/unreachable_glyphs>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    The following glyphs could not be reached by codepoint or substitution rules:

    - foundryicon
    

    [code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>
🔥 CutiveMono-Regular.ttf
  • 🔥 FAIL

    The following glyphs have no contours even though they were expected to have some:

    - Glyph name: uni2074	Expected: 1 or 2
    
    - Glyph name: uniFB00	Expected: 1 or 2
    
    - Glyph name: uniFB03	Expected: 1, 2, 3 or 4
    
    - Glyph name: uniFB04	Expected: 1, 2 or 3
    

    [code: no-contour]

  • ⚠️ 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: percent	Contours detected: 4	Expected: 5
    
    - Glyph name: asterisk	Contours detected: 6	Expected: 1 or 4
    
    - Glyph name: uni00AD	Contours detected: 1	Expected: 0
    
    - Glyph name: uni01CA	Contours detected: 1	Expected: 2
    
    - Glyph name: uni01F5	Contours detected: 4	Expected: 3
    
    - Glyph name: asterisk	Contours detected: 6	Expected: 1 or 4
    
    - Glyph name: percent	Contours detected: 4	Expected: 5
    
    - Glyph name: uni00AD	Contours detected: 1	Expected: 0
    
    - Glyph name: uni01CA	Contours detected: 1	Expected: 2
    

    [code: contour-count]

Does the font contain a soft hyphen?

Check ID: <FontBakeryCheck:com.google.fonts/check/soft_hyphen>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    This font has a 'Soft Hyphen' character. [code: softhyphen]

Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)

Check ID: <FontBakeryCheck:com.google.fonts/check/alt_caron:googlefonts>
🔥 CutiveMono-Regular.ttf
  • 🔥 FAIL

    Lcaron uses component comma. [code: bad-mark]

  • 🔥 FAIL

    dcaron 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.name

🔥⏩⏩

Checking correctness of monospaced metadata.

Check ID: <FontBakeryCheck:com.google.fonts/check/monospace>
🔥 CutiveMono-Regular.ttf
  • 🔥 FAIL

    On monospaced fonts, the value of post.isFixedPitch must be set to a non-zero value (meaning 'fixed width monospaced'), but got 0 instead. [code: mono-bad-post-isFixedPitch]

  • 🔥 FAIL

    The PANOSE numbers are incorrect for a monospaced font. Note: Family Type is set to 0, which does not seem right. [code: mono-bad-panose]

  • ⚠️ WARN

    The OpenType spec recomments at https://learn.microsoft.com/en-us/typography/opentype/spec/recom#hhea-table that hhea.numberOfHMetrics be set to 3 but this font has 421 instead. Please read https://github.com/fonttools/fonttools/issues/3014 to decide whether this makes sense for your font. [code: bad-numberOfHMetrics]

Section: fontbakery.profiles.dsig

⚠️

Does the font have a DSIG table?

Check ID: <FontBakeryCheck:com.google.fonts/check/dsig>
⚠️ CutiveMono-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.gpos

⚠️

Does GPOS table have kerning information? This check skips monospaced fonts as defined by post.isFixedPitch value

Check ID: <FontBakeryCheck:com.google.fonts/check/gpos_kerning_info>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    GPOS table lacks kerning information. [code: lacks-kern-info]

Section: fontbakery.profiles.glyf

⚠️

Check for points out of bounds.

Check ID: <FontBakeryCheck:com.google.fonts/check/points_out_of_bounds>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    The following glyphs have coordinates which are out of bounds: * ('Zacute', 1045, 28) * ('Zcaron', 1045, 28) and ('Zdotaccent', 1045, 28)

    This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message. [code: points-out-of-bounds]

Section: Shaping Checks

⚠️⚠️⏩⏩⏩

Ensure dotted circle glyph is present and can attach marks.

Check ID: <FontBakeryCheck:com.google.fonts/check/dotted_circle>
⚠️ CutiveMono-Regular.ttf
  • ⚠️ WARN

    No dotted circle glyph present [code: missing-dotted-circle]

Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.

Check ID: <FontBakeryCheck:com.google.fonts/check/soft_dotted>
⚠️ CutiveMono-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: Lithuanian (Latn, 2,357,094 speakers), Aghem (Latn, 38,843 speakers), Belarusian (Cyrl, 10,064,517 speakers), Basaa (Latn, 332,940 speakers), Navajo (Latn, 166,319 speakers), Igbo (Latn, 27,823,640 speakers), Dutch (Latn, 31,709,104 speakers), Ukrainian (Cyrl, 29,273,587 speakers). [code: soft-dotted]