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 7 17 61 8 148
0% 4% 10% 35% 5% 84%

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>
🔥 FrancoisOne-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 should end in a linebreak.

Check ID: <FontBakeryCheck:com.google.fonts/check/description/eof_linebreak>
⚠️ FrancoisOne-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>
⚠️ FrancoisOne-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>
🔥 FrancoisOne-Regular.ttf
  • 🔥 FAIL

    Missing required codepoints:

    - 0x0312 (COMBINING TURNED COMMA ABOVE)
    

    [code: missing-codepoints]

Check for codepoints not covered by METADATA subsets.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/unreachable_subsetting>
⚠️ FrancoisOne-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+0272 LATIN SMALL LETTER N WITH LEFT HOOK: not included in any glyphset definition
    • U+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh
    • 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+0300 COMBINING GRAVE ACCENT: try adding one of: coptic, cherokee, tai-le
    • U+0301 COMBINING ACUTE ACCENT: try adding one of: coptic, cherokee, tifinagh, tai-le
    • U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: coptic, cherokee, tifinagh
    • U+0303 COMBINING TILDE: not included in any glyphset definition
    • U+0304 COMBINING MACRON: try adding one of: coptic, cherokee, gothic, tifinagh
    • U+0306 COMBINING BREVE: try adding tifinagh
    • U+0307 COMBINING DOT ABOVE: try adding one of: coptic, canadian-aboriginal, tifinagh, tai-le, malayalam
    • U+0308 COMBINING DIAERESIS: try adding one of: coptic, gothic, tai-le
    • U+0309 COMBINING HOOK ABOVE: try adding tifinagh
    • U+030A COMBINING RING ABOVE: not included in any glyphset definition
    • U+030B COMBINING DOUBLE ACUTE ACCENT: try adding cherokee
    • U+030C COMBINING CARON: try adding one of: cherokee, tai-le
    • U+030F COMBINING DOUBLE GRAVE ACCENT: not included in any glyphset definition
    • U+0311 COMBINING INVERTED BREVE: try adding coptic
    • U+031B COMBINING HORN: not included in any glyphset definition
    • U+0323 COMBINING DOT BELOW: try adding one of: malayalam, coptic, cherokee, tifinagh
    • U+0324 COMBINING DIAERESIS BELOW: try adding cherokee
    • 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+032E COMBINING BREVE BELOW: not included in any glyphset definition
    • U+0331 COMBINING MACRON BELOW: try adding one of: cherokee, gothic, tifinagh
    • U+0335 COMBINING SHORT STROKE OVERLAY: 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+2116 NUMERO SIGN: try adding cyrillic
    • 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+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, vietnamese [code: unreachable-subsetting]

Check license file has good copyright string.

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

    First line in license file is:

    "copyright 2011 the francois one project authors (contact@sansoxygen.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>
⚠️ FrancoisOne-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>
⚠️ FrancoisOne-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>
🔥 FrancoisOne-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 2011 the francois one project authors (contact@sansoxygen.com)" [code: bad-notice-format]

Copyright notices match canonical pattern in fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/font_copyright>
🔥 FrancoisOne-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 2011 The Francois One Project Authors (contact@sansoxygen.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 2011 The Francois One Project Authors (contact@sansoxygen.com)" [code: bad-notice-format]

PPEM must be an integer on hinted fonts.

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

Are there caret positions declared for every ligature?

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

    This font lacks caret positioning values for these ligature glyphs: - f_f - f_f_l - fl

    [code: incomplete-caret-pos-data]

Is there kerning info for non-ligated sequences?

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

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

    - f + f
    
    - f + i
    
    - i + f
    
    - f + l
    
    - l + f
    
    - i + l [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>
⚠️ FrancoisOne-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>
⚠️ FrancoisOne-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 fonts have ScriptLangTags declared on the 'meta' table.

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

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

    - IJacute
    
    - ijacute
    
    - uni03020300.case
    
    - uni03020303.case
    
    - uni03020309.case
    
    - uni03060300
    
    - uni03060301
    
    - uni03060303
    
    - uni03060309
    
    - zero.zero
    

    [code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>
⚠️ FrancoisOne-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: uni00AD	Contours detected: 1	Expected: 0
    
    - Glyph name: aring	Contours detected: 3	Expected: 4
    
    - Glyph name: ldot	Contours detected: 1	Expected: 2
    
    - Glyph name: uni1EB7	Contours detected: 3	Expected: 4
    
    - Glyph name: notequal	Contours detected: 2	Expected: 1
    
    - Glyph name: aring	Contours detected: 3	Expected: 4
    
    - Glyph name: fi	Contours detected: 2	Expected: 3
    
    - Glyph name: fl	Contours detected: 1	Expected: 2
    
    - Glyph name: ldot	Contours detected: 1	Expected: 2
    
    - Glyph name: notequal	Contours detected: 2	Expected: 1
    
    - Glyph name: uni00AD	Contours detected: 1	Expected: 0
    
    - Glyph name: uni1EB7	Contours detected: 3	Expected: 4
    

    [code: contour-count]

Does the font contain a soft hyphen?

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

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

    Width = 417: plus

    Width = 477: less, greater

    Width = 385: logicalnot

    Width = 423: plusminus

    Width = 418: multiply

    Width = 389: divide

    Width = 404: approxequal

    Width = 478: lessequal, greaterequal [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>
🔥 FrancoisOne-Regular.ttf
  • 🔥 FAIL

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

  • 🔥 FAIL

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

  • 🔥 FAIL

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

  • ⚠️ WARN

    dcaron 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>
⚠️ FrancoisOne-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: Shaping Checks

⚠️⚠️⏩⏩⏩

Ensure dotted circle glyph is present and can attach marks.

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

    The dot of soft dotted characters used in orthographies must disappear in the following strings: j̀ j́ j̃ j̄ j̈ j̑ į̀ į́ į̂ į̃ į̄ į̌ ị̀ ị́ ị̂ ị̃ ị̄

    The dot of soft dotted characters should disappear in other cases, for example: i̵̇ i̵̊ i̵̋ ǐ̵ j̆ j̇ j̉ j̊ j̋ ǰ j̏ j̵̀ j̵́ j̵̃ j̵̄ j̵̆ j̵̇ j̵̈ j̵̉ j̵̊

    Your font fully covers the following languages that require the soft-dotted feature: Igbo (Latn, 27,823,640 speakers).

    Your font does not cover the following languages that require the soft-dotted feature: Basaa (Latn, 332,940 speakers), Belarusian (Cyrl, 10,064,517 speakers), Aghem (Latn, 38,843 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Dutch (Latn, 31,709,104 speakers), Lithuanian (Latn, 2,357,094 speakers), Navajo (Latn, 166,319 speakers). [code: soft-dotted]