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 15 63 8 148
0% 4% 8% 36% 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>
🔥 Bahiana-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>
🔥 Bahiana-Regular.ttf
  • 🔥 FAIL

    Missing required codepoints:

    - 0x0312 (COMBINING TURNED COMMA ABOVE)


- 0x0328 (COMBINING OGONEK)

    [code: missing-codepoints]

Check for codepoints not covered by METADATA subsets.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/unreachable_subsetting>
⚠️ Bahiana-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, yi, canadian-aboriginal
    • U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
    • U+02D8 BREVE: try adding one of: yi, canadian-aboriginal
    • U+02D9 DOT ABOVE: try adding one of: yi, canadian-aboriginal
    • U+02DB OGONEK: try adding one of: yi, canadian-aboriginal
    • U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
    • U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: cherokee, tifinagh, math, coptic
    • U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh
    • U+0307 COMBINING DOT ABOVE: try adding one of: tai-le, malayalam, math, old-permic, canadian-aboriginal, syriac, tifinagh, coptic
    • 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+0326 COMBINING COMMA BELOW: not included in any glyphset definition
    • U+0327 COMBINING CEDILLA: not included in any glyphset definition
    • U+0394 GREEK CAPITAL LETTER DELTA: try adding one of: math, greek, elbasan
    • U+03A9 GREEK CAPITAL LETTER OMEGA: try adding one of: math, greek, elbasan
    • U+03BC GREEK SMALL LETTER MU: try adding one of: math, greek
    • U+03C0 GREEK SMALL LETTER PI: try adding one of: math, greek, yi
    • U+1EB8 LATIN CAPITAL LETTER E WITH DOT BELOW: try adding vietnamese
    • U+1EB9 LATIN SMALL LETTER E WITH DOT BELOW: try adding vietnamese
    • U+1EBC LATIN CAPITAL LETTER E WITH TILDE: try adding vietnamese
    • U+1EBD LATIN SMALL LETTER E WITH TILDE: try adding vietnamese
    • U+1ECA LATIN CAPITAL LETTER I WITH DOT BELOW: try adding vietnamese
    • U+1ECB LATIN SMALL LETTER I WITH DOT BELOW: try adding vietnamese
    • U+1ECC LATIN CAPITAL LETTER O WITH DOT BELOW: try adding vietnamese
    • U+1ECD LATIN SMALL LETTER O WITH DOT BELOW: try adding vietnamese
    • U+1EE4 LATIN CAPITAL LETTER U WITH DOT BELOW: try adding vietnamese
    • U+1EE5 LATIN SMALL LETTER U WITH DOT BELOW: try adding vietnamese
    • U+2003 EM SPACE: try adding nushu
    • U+2004 THREE-PER-EM SPACE: not included in any glyphset definition
    • U+2005 FOUR-PER-EM SPACE: not included in any glyphset definition
    • U+2021 DOUBLE DAGGER: try adding adlam
    • U+2030 PER MILLE SIGN: try adding adlam
    • U+2126 OHM SIGN: not included in any glyphset definition
    • U+212E ESTIMATED SYMBOL: not included in any glyphset definition
    • U+2153 VULGAR FRACTION ONE THIRD: not included in any glyphset definition
    • U+2154 VULGAR FRACTION TWO THIRDS: not included in any glyphset definition
    • U+215B VULGAR FRACTION ONE EIGHTH: 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: math, symbols, 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: math, symbols
    • 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 [code: unreachable-subsetting]

Check license file has good copyright string.

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

    First line in license file is:

    "copyright 2016 the bahiana project authors (omnibus.type@gmail.com)"

    which does not match the expected format, similar to:

    "Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]

Check OFL body text is correct.

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

    The OFL.txt body text is incorrect. Please use https://github.com/googlefonts/Unified-Font-Repository/blob/main/OFL.txt as a template. You should only modify the first line. [code: incorrect-ofl-body-text]

Check copyright namerecords match license file.

Check ID: <FontBakeryCheck:com.google.fonts/check/name/license>
⚠️ Bahiana-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>
⚠️ Bahiana-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>
🔥 Bahiana-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 2016 the bahiana project authors (omnibus.type@gmail.com)" [code: bad-notice-format]

Copyright notices match canonical pattern in fonts

Check ID: <FontBakeryCheck:com.google.fonts/check/font_copyright>
🔥 Bahiana-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 2016 The Bahiana Project Authors (omnibus.type@gmail.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 2016 The Bahiana Project Authors (omnibus.type@gmail.com)" [code: bad-notice-format]

PPEM must be an integer on hinted fonts.

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

    This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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>
⚠️ Bahiana-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>
⚠️ Bahiana-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.

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

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ WARN

    The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

  • ⚠️ 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.

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

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

    - Iacute_J.loclNLD

- baraccent

- baraccentlong

- baraccentmedium

- caron.alt

- commaaccentinvert

- dotbelow

- iacute_j.loclNLD

    [code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>
⚠️ Bahiana-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: b	Contours detected: 3	Expected: 2

- Glyph name: e	Contours detected: 1	Expected: 2

- Glyph name: g	Contours detected: 1	Expected: 2 or 3

- Glyph name: i	Contours detected: 1	Expected: 2

- Glyph name: j	Contours detected: 1	Expected: 2

- Glyph name: r	Contours detected: 2	Expected: 1

- Glyph name: uni00AD	Contours detected: 1	Expected: 0

- Glyph name: ae	Contours detected: 2	Expected: 3

- Glyph name: egrave	Contours detected: 2	Expected: 3

- Glyph name: eacute	Contours detected: 2	Expected: 3

- Glyph name: ecircumflex	Contours detected: 2	Expected: 3

- Glyph name: edieresis	Contours detected: 3	Expected: 4

- Glyph name: emacron	Contours detected: 2	Expected: 3

- Glyph name: ebreve	Contours detected: 2	Expected: 3

- Glyph name: edotaccent	Contours detected: 2	Expected: 3

- Glyph name: eogonek	Contours detected: 1	Expected: 2

- Glyph name: ecaron	Contours detected: 2	Expected: 3

- Glyph name: gcircumflex	Contours detected: 2	Expected: 3 or 4

- Glyph name: gbreve	Contours detected: 2	Expected: 3 or 4

- Glyph name: gdotaccent	Contours detected: 2	Expected: 3 or 4

- Glyph name: gcommaaccent	Contours detected: 2	Expected: 3 or 4

- Glyph name: hbar	Contours detected: 2	Expected: 1

- Glyph name: iogonek	Contours detected: 1	Expected: 2 or 3

- Glyph name: ij	Contours detected: 2	Expected: 3 or 4

- Glyph name: oe	Contours detected: 2	Expected: 3

- Glyph name: racute	Contours detected: 3	Expected: 2

- Glyph name: rcommaaccent	Contours detected: 3	Expected: 2

- Glyph name: rcaron	Contours detected: 3	Expected: 2

- Glyph name: uni01C9	Contours detected: 2	Expected: 3

- Glyph name: uni01CC	Contours detected: 2	Expected: 3

- Glyph name: aeacute	Contours detected: 3	Expected: 4

- Glyph name: uni1E5B	Contours detected: 3	Expected: 2

- Glyph name: uni1EB9	Contours detected: 2	Expected: 3

- Glyph name: uni1EBD	Contours detected: 2	Expected: 3

- Glyph name: uni1ECB	Contours detected: 2	Expected: 3

- Glyph name: ae	Contours detected: 2	Expected: 3

- Glyph name: aeacute	Contours detected: 3	Expected: 4

- Glyph name: b	Contours detected: 3	Expected: 2

- Glyph name: e	Contours detected: 1	Expected: 2

- Glyph name: eacute	Contours detected: 2	Expected: 3

- Glyph name: ebreve	Contours detected: 2	Expected: 3

- Glyph name: ecaron	Contours detected: 2	Expected: 3

- Glyph name: ecircumflex	Contours detected: 2	Expected: 3

- Glyph name: edieresis	Contours detected: 3	Expected: 4

- Glyph name: edotaccent	Contours detected: 2	Expected: 3

- Glyph name: egrave	Contours detected: 2	Expected: 3

- Glyph name: emacron	Contours detected: 2	Expected: 3

- Glyph name: eogonek	Contours detected: 1	Expected: 2

- Glyph name: fi	Contours detected: 1	Expected: 3

- Glyph name: fl	Contours detected: 1	Expected: 2

- Glyph name: g	Contours detected: 1	Expected: 2 or 3

- Glyph name: gbreve	Contours detected: 2	Expected: 3 or 4

- Glyph name: gcircumflex	Contours detected: 2	Expected: 3 or 4

- Glyph name: gdotaccent	Contours detected: 2	Expected: 3 or 4

- Glyph name: hbar	Contours detected: 2	Expected: 1

- Glyph name: i	Contours detected: 1	Expected: 2

- Glyph name: ij	Contours detected: 2	Expected: 3 or 4

- Glyph name: iogonek	Contours detected: 1	Expected: 2 or 3

- Glyph name: j	Contours detected: 1	Expected: 2

- Glyph name: oe	Contours detected: 2	Expected: 3

- Glyph name: r	Contours detected: 2	Expected: 1

- Glyph name: racute	Contours detected: 3	Expected: 2

- Glyph name: rcaron	Contours detected: 3	Expected: 2

- Glyph name: uni00AD	Contours detected: 1	Expected: 0

- Glyph name: uni01C9	Contours detected: 2	Expected: 3

- Glyph name: uni01CC	Contours detected: 2	Expected: 3

- Glyph name: uni1E5B	Contours detected: 3	Expected: 2

- Glyph name: uni1EB9	Contours detected: 2	Expected: 3

- Glyph name: uni1EBD	Contours detected: 2	Expected: 3

- Glyph name: uni1ECB	Contours detected: 2	Expected: 3

    [code: contour-count]

Does the font contain a soft hyphen?

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

    Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

  • ⚠️ 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

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

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

Section: Shaping Checks

⚠️⏩⏩⏩⏩

Ensure dotted circle glyph is present and can attach marks.

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

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