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 21 14 66 8 132
0% 12% 8% 37% 4% 74%

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 font file include unacceptable control character glyphs?

Check ID: <FontBakeryCheck:com.google.fonts/check/family/control_chars>
🔥 Family check
  • 🔥 FAIL

    The following unacceptable control characters were identified: /Users/simon/others-repos/fonts/ofl/limelight/Limelight-Regular.ttf: uni0001, uni0002, uni0003, uni0004, uni0005, uni0006, uni0007, uni0008, uni0009, uni0010, uni0011, uni0012, uni0013, uni0014, uni0015, uni0016, uni0017, uni0018, uni0019 [code: unacceptable]

Does DESCRIPTION file contain a upstream Git repo URL?

Check ID: <FontBakeryCheck:com.google.fonts/check/description/git_url>
🔥 Limelight-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]

Check Google Fonts glyph coverage.

Check ID: <FontBakeryCheck:com.google.fonts/check/glyph_coverage>
🔥 Limelight-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>
⚠️ Limelight-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+0001 : not included in any glyphset definition
    • U+0002 : not included in any glyphset definition
    • U+0003 : not included in any glyphset definition
    • U+0004 : not included in any glyphset definition
    • U+0005 : not included in any glyphset definition
    • U+0006 : not included in any glyphset definition
    • U+0007 : not included in any glyphset definition
    • U+0008 : not included in any glyphset definition
    • U+0009 : not included in any glyphset definition
    • U+0010 : not included in any glyphset definition
    • U+0011 : not included in any glyphset definition
    • U+0012 : not included in any glyphset definition
    • U+0013 : not included in any glyphset definition
    • U+0014 : not included in any glyphset definition
    • U+0015 : not included in any glyphset definition
    • U+0016 : not included in any glyphset definition
    • U+0017 : not included in any glyphset definition
    • U+0018 : not included in any glyphset definition
    • U+0019 : 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+0394 GREEK CAPITAL LETTER DELTA: try adding greek
    • U+03A9 GREEK CAPITAL LETTER OMEGA: try adding greek
    • U+03BC GREEK SMALL LETTER MU: try adding greek
    • U+03C0 GREEK SMALL LETTER PI: 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+2126 OHM SIGN: not included in any glyphset definition
    • U+2202 PARTIAL DIFFERENTIAL: 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+2211 N-ARY SUMMATION: not included in any glyphset definition
    • U+221A SQUARE ROOT: 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: menu, latin, latin-ext [code: unreachable-subsetting]

Check license file has good copyright string.

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

    First line in license file is:

    "copyright (c) 2011 by sorkin type co (www.sorkintype.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>
🔥 Limelight-Regular.ttf
  • 🔥 FAIL

    License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 1 (MACINTOSH) is not specified for that. Value was: "This Font Software is licensed under the SIL Open Font License, Version 1.1." Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL" [code: wrong]

  • 🔥 FAIL

    License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 (WINDOWS) is not specified for that. Value was: "This Font Software is licensed under the SIL Open Font License, Version 1.1." Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL" [code: wrong]

METADATA.pb subsets should be alphabetically ordered.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/subsets_order>
🔥 Limelight-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]

Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.

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

    Unmatched postscript name in font: TTF has "Limelight-Regular" while METADATA.pb has "Limelight". [code: mismatch]

  • 🔥 FAIL

    Unmatched postscript name in font: TTF has "Limelight-Regular" while METADATA.pb has "Limelight". [code: mismatch]

METADATA.pb font.full_name value matches fullname declared on the name table?

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

    Unmatched fullname in font: TTF has "Limelight Regular" while METADATA.pb has "Limelight". [code: mismatch]

  • 🔥 FAIL

    Unmatched fullname in font: TTF has "Limelight Regular" while METADATA.pb has "Limelight". [code: mismatch]

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

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

    METADATA.pb font filename = "Limelight-Regular.ttf" does not match post_script_name="Limelight". [code: mismatch]

Copyright notices match canonical pattern in METADATA.pb

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>
🔥 Limelight-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) 2010 by sorkin type co (eben@eyebytes.com) with reserved font name limelight. this font software is licensed under the sil open font license, version 1.1. this license is available with a faq at: http://scripts.sil.org/ofl" [code: bad-notice-format]

Copyright notices match canonical pattern in fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/font_copyright>
🔥 Limelight-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) 2010 by Sorkin Type Co with Reserved Font Name Limelight.

    This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL" [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) 2010 by Sorkin Type Co with Reserved Font Name Limelight.

    This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL" [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>
⚠️ Limelight-Regular.ttf
  • ⚠️ WARN

    METADATA.pb: copyright field ("Copyright (c) 2010 by Sorkin Type Co (eben@eyebytes.com) with Reserved Font Name Limelight. This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]

METADATA.pb font.name and font.full_name fields match the values declared on the name table?

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

    METADATA.pb: Fullname "Limelight" does not match name table entry "Limelight Regular"! [code: fullname-mismatch]

METADATA.pb weight matches postScriptName for static fonts.

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

    METADATA.pb: Mismatch between postScriptName ("Limelight") and weight value (400). The name must be ended with "Regular" or "Italic".

METADATA.pb: Check URL on copyright string is the same as in repository_url field.

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

    Value of repository_url field is

    But font copyright string has: http://scripts.sil.org/OFL [code: mismatch]

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>
🔥 Limelight-Regular.ttf
  • 🔥 FAIL

    Copyright field for this font on METADATA.pb ("Copyright (c) 2010 by Sorkin Type Co (eben@eyebytes.com) with Reserved Font Name Limelight. This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL") differs from a copyright notice entry on the name table: "Copyright (c) 2010 by Sorkin Type Co with Reserved Font Name Limelight.

    This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL" [code: mismatch]

  • 🔥 FAIL

    Copyright field for this font on METADATA.pb ("Copyright (c) 2010 by Sorkin Type Co (eben@eyebytes.com) with Reserved Font Name Limelight. This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http://scripts.sil.org/OFL") differs from a copyright notice entry on the name table: "Copyright (c) 2010 by Sorkin Type Co with Reserved Font Name Limelight.

    This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is copied below, and is also available with a FAQ at: http://scripts.sil.org/OFL" [code: mismatch]

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

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

Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.

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

    Limelight Regular: OS/2 sTypoDescender is -634 when it should be -629 [code: bad-typo-descender]

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

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

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

Section: Universal

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

Checking OS/2 usWinAscent & usWinDescent.

Check ID: <FontBakeryCheck:com.google.fonts/check/family/win_ascent_and_descent>
🔥 Limelight-Regular.ttf
  • 🔥 FAIL

    OS/2.usWinDescent value should be equal or greater than 636, but got 629 instead [code: descent]

Checking OS/2 Metrics match hhea Metrics.

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

    OS/2 sTypoDescender (-634) and hhea descent (-629) must be equal. [code: descender]

Font contains '.notdef' as its first glyph?

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

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

Font has **proper** whitespace glyph names?

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

    Glyph 0x00A0 is called "nonbreakingspace": Change to "uni00A0" [code: not-recommended-00a0]

Are there unwanted tables?

Check ID: <FontBakeryCheck:com.google.fonts/check/unwanted_tables>
🔥 Limelight-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>
⚠️ Limelight-Regular.ttf
  • ⚠️ WARN

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

    - acute.cap
    
    - breve.cap
    
    - caron.cap
    
    - caronvertical
    
    - circumflex.cap
    
    - commaaccent
    
    - dieresis.cap
    
    - dotaccent.cap
    
    - foundryicon
    
    - grave.cap
    
    - hungarumlaut.cap
    
    - macron.cap
    
    - nonmarkingreturn
    
    - 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>
⚠️ Limelight-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: three	Contours detected: 2	Expected: 1
    
    - Glyph name: eight	Contours detected: 1	Expected: 3
    
    - Glyph name: threesuperior	Contours detected: 2	Expected: 1
    
    - Glyph name: threequarters	Contours detected: 5	Expected: 3 or 4
    
    - Glyph name: Oslash	Contours detected: 4	Expected: 2 or 3
    
    - Glyph name: oslash	Contours detected: 2	Expected: 3
    
    - Glyph name: Racute	Contours detected: 2	Expected: 3
    
    - Glyph name: Rcommaaccent	Contours detected: 2	Expected: 3
    
    - Glyph name: Rcaron	Contours detected: 2	Expected: 3
    
    - Glyph name: uni1E02	Contours detected: 3	Expected: 4
    
    - Glyph name: uni1E56	Contours detected: 2	Expected: 3
    
    - Glyph name: Oslash	Contours detected: 4	Expected: 2 or 3
    
    - Glyph name: Racute	Contours detected: 2	Expected: 3
    
    - Glyph name: Rcaron	Contours detected: 2	Expected: 3
    
    - Glyph name: eight	Contours detected: 1	Expected: 3
    
    - Glyph name: oslash	Contours detected: 2	Expected: 3
    
    - Glyph name: three	Contours detected: 2	Expected: 1
    
    - Glyph name: threequarters	Contours detected: 5	Expected: 3 or 4
    
    - Glyph name: uni1E02	Contours detected: 3	Expected: 4
    
    - Glyph name: uni1E56	Contours detected: 2	Expected: 3
    

    [code: contour-count]

Does the font contain a soft hyphen?

Check ID: <FontBakeryCheck:com.google.fonts/check/soft_hyphen>
⚠️ Limelight-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>
⚠️ Limelight-Regular.ttf
  • ⚠️ WARN

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

    Width = 1014: plus, equal, notequal

    Width = 935: greater, less

    Width = 1078: logicalnot

    Width = 1035: plusminus

    Width = 884: multiply

    Width = 1021: approxequal [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>
⚠️ Limelight-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.os2

⚠️⏩

Check if OS/2 xAvgCharWidth is correct.

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

    OS/2 xAvgCharWidth is 1245 but it should be 1231 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]

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

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