FontBakery Check 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	5	19	61	8	148
0%	3%	11%	35%	5%	84%

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

Meaning of check results:

💥 An ERROR is something wrong with FontBakery itself, possibly a bug.
🔥 A FAIL is a problem with the font that must be fixed.
⚠️ A WARN is something that you should consider addressing.
ℹ️ An INFO result simply prints something useful. Typically stats.
✅ A PASS means the font looks good for the given checking routine.
⏩ And a SKIP happens when the check does not apply to the given font.

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 broken links?

Check ID: <FontBakeryCheck:com.google.fonts/check/description/broken_links>

🔥 PoiretOne-Regular.ttf

🔥 FAIL
Found an email address: mailto:denis.masharov@gmail.com [code: email]

Does DESCRIPTION file contain a upstream Git repo URL?

Check ID: <FontBakeryCheck:com.google.fonts/check/description/git_url>

🔥 PoiretOne-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>

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

🔥 PoiretOne-Regular.ttf

🔥 FAIL

Missing required codepoints:

- 0x0132 (LATIN CAPITAL LIGATURE IJ)


- 0x0133 (LATIN SMALL LIGATURE IJ)

[code: missing-codepoints]

Check for codepoints not covered by METADATA subsets.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/unreachable_subsetting>

⚠️ PoiretOne-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, 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+0300 COMBINING GRAVE ACCENT: try adding one of: cherokee, coptic, tai-le
- U+0301 COMBINING ACUTE ACCENT: try adding one of: cherokee, coptic, tai-le, tifinagh
- U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: cherokee, coptic, tifinagh
- U+0303 COMBINING TILDE: not included in any glyphset definition
- U+0304 COMBINING MACRON: try adding one of: gothic, cherokee, coptic, tifinagh
- U+0306 COMBINING BREVE: try adding tifinagh
- U+0307 COMBINING DOT ABOVE: try adding one of: tai-le, tifinagh, malayalam, canadian-aboriginal, coptic
- U+0308 COMBINING DIAERESIS: try adding one of: gothic, coptic, 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+0312 COMBINING TURNED COMMA ABOVE: not included in any glyphset definition
- U+031B COMBINING HORN: not included in any glyphset definition
- U+0323 COMBINING DOT BELOW: try adding one of: cherokee, coptic, malayalam, 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+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: cyrillic, cyrillic-ext, latin, latin-ext, menu, vietnamese [code: unreachable-subsetting]

Check copyright namerecords match license file.

Check ID: <FontBakeryCheck:com.google.fonts/check/name/license>

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

⚠️ PoiretOne-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: Check URL on copyright string is the same as in repository_url field.

Check ID: <FontBakeryCheck:com.google.fonts/check/metadata/consistent_repo_urls>

🔥 PoiretOne-Regular.ttf

🔥 FAIL
Value of repository_url field is

But font copyright string has: https://github.com/alexeiva/poiretone [code: mismatch]

Glyphs are similiar to Google Fonts version?

Check ID: <FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>

⚠️ PoiretOne-Regular.ttf

⚠️ WARN
Following glyphs differ greatly from Google Fonts version: * .notdef * currency and uni00AD

PPEM must be an integer on hinted fonts.

Check ID: <FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>

🔥 PoiretOne-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>

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

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

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

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

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

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

⚠️ PoiretOne-Regular.ttf

⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
```
- f_f_ij

- f_ij

- uni0304.i

- uni0326.alt

- uni041B.sso1
```
[code: unreachable-glyphs]

Check if each glyph has the recommended amount of contours.

Check ID: <FontBakeryCheck:com.google.fonts/check/contour_count>

⚠️ PoiretOne-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: at	Contours detected: 4	Expected: 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

- Glyph name: at	Contours detected: 4	Expected: 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[code: contour-count]

Does the font contain a soft hyphen?

Check ID: <FontBakeryCheck:com.google.fonts/check/soft_hyphen>

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

⚠️ PoiretOne-Regular.ttf

⚠️ WARN
The most common width is 408 among a set of 2 math glyphs. The following math glyphs have a different width, though:

Width = 341: plus

Width = 411: notequal, equal

Width = 410: logicalnot

Width = 451: plusminus

Width = 393: multiply

Width = 461: divide

Width = 391: minus

Width = 533: approxequal

Width = 463: greaterequal, lessequal [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>

⚠️ PoiretOne-Regular.ttf

⚠️ WARN
Lcaron 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>

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

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

⚠️ PoiretOne-Regular.ttf

⚠️ WARN
The dot of soft dotted characters used in orthographies must disappear in the following strings: į̀ į́ į̂ į̃ į̄ į̌ і́ ị̀ ị́ ị̂ ị̃ ị̄

The dot of soft dotted characters should disappear in other cases, for example: i̦̇ i̦̊ ǐ̦ i̦̒ j̦̃ j̦̆ j̦̇ j̦̉ j̦̊ ǰ̦ j̦̏ j̦̑ j̦̒ į̆ į̇ į̈ į̉ į̊ į̋ į̏

Your font fully covers the following languages that require the soft-dotted feature: Dutch (Latn, 31,709,104 speakers), Navajo (Latn, 166,319 speakers).

Your font does not cover the following languages that require the soft-dotted feature: Ukrainian (Cyrl, 29,273,587 speakers), Basaa (Latn, 332,940 speakers), Lithuanian (Latn, 2,357,094 speakers), Belarusian (Cyrl, 10,064,517 speakers), Aghem (Latn, 38,843 speakers), Igbo (Latn, 27,823,640 speakers). [code: soft-dotted]