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 13 19 64 8 137
0% 7% 11% 37% 5% 79%

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

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

Does DESCRIPTION file contain a upstream Git repo URL?

Check ID: <FontBakeryCheck:com.google.fonts/check/description/git_url>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    Please host your font project on a public Git repo (such as GitHub or GitLab) and place a link in the DESCRIPTION.en_us.html file. [code: lacks-git-url]

DESCRIPTION.en_us.html must have more than 200 bytes.

Check ID: <FontBakeryCheck:com.google.fonts/check/description/min_length>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    DESCRIPTION.en_us.html must have size larger than 200 bytes. [code: too-short]

DESCRIPTION.en_us.html should end in a linebreak.

Check ID: <FontBakeryCheck:com.google.fonts/check/description/eof_linebreak>
⚠️ JockeyOne-Regular.ttf
  • ⚠️ WARN

    The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

Check Google Fonts glyph coverage.

Check ID: <FontBakeryCheck:com.google.fonts/check/glyph_coverage>
🔥 JockeyOne-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)
    
    
    - 0x0307 (COMBINING DOT ABOVE)
    
    
    - 0x0302 (COMBINING CIRCUMFLEX ACCENT)
    
    
    - 0x030C (COMBINING CARON)
    
    
    - 0x0306 (COMBINING BREVE)
    
    
    - 0x030A (COMBINING RING ABOVE)
    
    
    - 0x0303 (COMBINING TILDE)
    
    
    - 0x0312 (COMBINING TURNED COMMA ABOVE)
    
    
    - 0x0326 (COMBINING COMMA BELOW)
    
    
    - 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>
⚠️ JockeyOne-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+0002 : not included in any glyphset definition
    • U+02C7 CARON: try adding one of: tifinagh, canadian-aboriginal
    • U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
    • 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+2021 DOUBLE DAGGER: not included in any glyphset definition
    • U+2030 PER MILLE SIGN: not included in any glyphset definition
    • U+2219 BULLET OPERATOR: try adding tai-tham
    • 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+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: menu, latin, latin-ext [code: unreachable-subsetting]

Check license file has good copyright string.

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

    First line in license file is:

    "copyright (c) 2011, typetogether (www.type-together.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.

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

METADATA.pb subsets should be alphabetically ordered.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/subsets_order>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'latin', 'latin-ext'] and expected ['latin', 'latin-ext', 'menu'] [code: not-sorted]

METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    METADATA.pb font full_name = "Jockey One" does not match post_script_name = "JockeyOne-Regular" [code: mismatch]

Copyright notices match canonical pattern in METADATA.pb

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>
🔥 JockeyOne-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) 2011, copyright (c) 2011, typetogether (www.type-together.com info@type-together.com), with reserved font names "jockey" and "jockey one"" [code: bad-notice-format]

Copyright notices match canonical pattern in fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/font_copyright>
🔥 JockeyOne-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) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com), with Reserved Font Names "Jockey" and "Jockey One"" [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) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com), with Reserved Font Names "Jockey" and "Jockey One"" [code: bad-notice-format]

Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>
⚠️ JockeyOne-Regular.ttf
  • ⚠️ WARN

    METADATA.pb: copyright field ("Copyright (c) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com info@type-together.com), with Reserved Font Names "Jockey" and "Jockey One"") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]

Check font names are correct

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

    Regular missing from full name [code: lacks-regular]

Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    Copyright field for this font on METADATA.pb ("Copyright (c) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com info@type-together.com), with Reserved Font Names "Jockey" and "Jockey One"") differs from a copyright notice entry on the name table: "Copyright (c) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com), with Reserved Font Names "Jockey" and "Jockey One"" [code: mismatch]

  • 🔥 FAIL

    Copyright field for this font on METADATA.pb ("Copyright (c) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com info@type-together.com), with Reserved Font Names "Jockey" and "Jockey One"") differs from a copyright notice entry on the name table: "Copyright (c) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com), with Reserved Font Names "Jockey" and "Jockey One"" [code: mismatch]

Are there caret positions declared for every ligature?

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

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

    GPOS table lacks kerning info for the following non-ligated sequences:

    - f + f
    
    - f + l
    
    - l + f
    
    - f + i
    
    - i + l
    
    - l + i
    
    - i + f
    
    - i + j
    
    - t + t [code: lacks-kern-info]
    

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>
⚠️ JockeyOne-Regular.ttf
  • ⚠️ WARN

    Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

Ensure METADATA.pb does not use escaped strings.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/escaped_strings>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    Found escaped chars at 'Copyright (c) 2011, Copyright (c) 2011, TypeTogether (www.type-together.com info@type-together.com), with Reserved Font Names '. Please use an unicode string instead. [code: escaped-strings]

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>
⚠️ JockeyOne-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>
🔥 JockeyOne-Regular.ttf
  • 🔥 FAIL

    OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/jockeyone/JockeyOne-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>
⚠️ JockeyOne-Regular.ttf
  • ⚠️ WARN

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

Ensure fonts do not contain any pre-production tables.

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

    This font file contains the following pre-production tables: FFTM [code: has-debugging-tables]

Section: Universal

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

Font contains '.notdef' as its first glyph?

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

    The '.notdef' glyph should contain a drawing, but it is blank. [code: notdef-is-blank]

Are there unwanted tables?

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

    The following unwanted font tables were found:

    • FFTM - Table contains redundant FontForge timestamp info

    They can be removed with the 'fix-unwanted-tables' script provided by gftools. [code: unwanted-tables]

Check font contains no unreachable glyphs

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

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

    - acute.cap
    
    - breve.cap
    
    - caron.alt
    
    - caron.cap
    
    - cedilla.cap
    
    - circumflex.cap
    
    - commaaccent
    
    - commaaccent.cap
    
    - dieresis.cap
    
    - dotaccent.cap
    
    - grave.cap
    
    - hungarumlaut.cap
    
    - hyphen.case
    
    - idotaccent
    
    - macron.cap
    
    - nonmarkingreturn
    
    - ogonek.cap
    
    - revcommaaccent
    
    - ring.cap
    
    - tilde.cap
    

    [code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>
⚠️ JockeyOne-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: plus	Contours detected: 2	Expected: 1
    
    - Glyph name: uni00AD	Contours detected: 1	Expected: 0
    
    - Glyph name: plusminus	Contours detected: 3	Expected: 1 or 2
    
    - Glyph name: multiply	Contours detected: 2	Expected: 1
    
    - Glyph name: oslash	Contours detected: 2	Expected: 3
    
    - Glyph name: Eng	Contours detected: 2	Expected: 1
    
    - Glyph name: Oslashacute	Contours detected: 3	Expected: 4
    
    - Glyph name: oslashacute	Contours detected: 3	Expected: 4
    
    - Glyph name: notequal	Contours detected: 3	Expected: 1
    
    - Glyph name: Eng	Contours detected: 2	Expected: 1
    
    - Glyph name: Oslashacute	Contours detected: 3	Expected: 4
    
    - Glyph name: fi	Contours detected: 2	Expected: 3
    
    - Glyph name: fl	Contours detected: 1	Expected: 2
    
    - Glyph name: multiply	Contours detected: 2	Expected: 1
    
    - Glyph name: notequal	Contours detected: 3	Expected: 1
    
    - Glyph name: oslash	Contours detected: 2	Expected: 3
    
    - Glyph name: oslashacute	Contours detected: 3	Expected: 4
    
    - Glyph name: plus	Contours detected: 2	Expected: 1
    
    - Glyph name: plusminus	Contours detected: 3	Expected: 1 or 2
    
    - Glyph name: uni00AD	Contours detected: 1	Expected: 0
    

    [code: contour-count]

Does the font contain a soft hyphen?

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

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

Check math signs have the same width.

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

    The most common width is 344 among a set of 6 math glyphs. The following math glyphs have a different width, though:

    Width = 379: less, lessequal, greater, greaterequal

    Width = 321: multiply

    Width = 472: approxequal

    Width = 414: notequal [code: width-outliers]

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>
⚠️ JockeyOne-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]

Section: fontbakery.profiles.dsig

⚠️

Does the font have a DSIG table?

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

⚠️

Check for points out of bounds.

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

    The following glyphs have coordinates which are out of bounds: * ('braceleft', 20, -116) * ('braceleft', 20, 768) * ('braceright', 228, 768) * ('braceright', 228, -116) * ('tilde', 320, 556) and ('tilde.cap', 320, 733)

    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]