github-actions[bot]
commented
1 week ago FontBakery report
fontbakery version: 0.12.7
Experimental checks
These won't break the CI job for now, but will become effective after some time if nobody raises any concern.
[2] Matemasie-Regular.ttf
All other checks
[22] Matemasie-Regular.ttf
🔥 FAIL Ensure the font supports case swapping for all its glyphs.
The following glyphs lack their case-swapping counterparts:
| Glyph present in the font | Missing case-swapping counterpart |
|---|---|
| U+01F9: LATIN SMALL LETTER N WITH GRAVE | U+01F8: LATIN CAPITAL LETTER N WITH GRAVE |
🔥 FAIL Checking OS/2 usWinAscent & usWinDescent.
OS/2.usWinDescent value should be equal or greater than 241, but got 230 instead
[code: descent]🔥 FAIL Name table records must not have trailing spaces.
Name table record with key = (3, 1, 1033, 1) has trailing spaces that must be removed: 'Matemasie '
[code: trailing-space]🔥 FAIL Checking with fontTools.ttx
WARNING: name id 256 missing from name table
* 🔥 **FAIL**WARNING: name id 257 missing from name table
* 🔥 **FAIL**WARNING: name id 258 missing from name table
* ℹ️ **INFO**While converting TTF into an XML file, ttx emited the messages listed below.
🔥 FAIL Space and non-breaking space have the same width?
Space and non-breaking space have differing width: The space glyph named space is 185 font units wide, non-breaking space named (uni00A0) is 220 font units wide, and both should be positive and the same. GlyphsApp has "Sidebearing arithmetic" (https://glyphsapp.com/tutorials/spacing) which allows you to set the non-breaking space width to always equal the space width.
[code: different-widths]🔥 FAIL METADATA.pb font.name and font.full_name fields match the values declared on the name table?
METADATA.pb Family name "Matemasie" does not match name table entry "Matemasie "!
[code: familyname-mismatch]🔥 FAIL METADATA.pb font.name value should be same as the family name declared on the name table.
Unmatched familyname in font: TTF has familyname = "Matemasie " while METADATA.pb has font.name = "Matemasie".
[code: mismatch]🔥 FAIL Is this a proper HTML snippet?
None does not include an HTML
tag.
[code: lacks-paragraph]🔥 FAIL Check copyright namerecords match license file.
License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 (WINDOWS) is not specified for that. Value was: "https://openfontlicense.org" 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://openfontlicense.org"
[code: wrong]🔥 FAIL Check font names are correct
Font names are incorrect:
| nameID | current | expected |
|---|---|---|
| Family Name | **Matemasie ** | Matemasie |
| Subfamily Name | Regular | Regular |
| Full Name | Matemasie Regular | Matemasie Regular |
| Postscript Name | Matemasie-Regular | Matemasie-Regular |
⚠️ WARN Check if each glyph has the recommended amount of contours.
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: germandbls Contours detected: 2 Expected: 1
- Glyph name: oslash Contours detected: 2 Expected: 3
- Glyph name: germandbls Contours detected: 2 Expected: 1
- Glyph name: oslash Contours detected: 2 Expected: 3
⚠️ WARN Check math signs have the same width.
The most common width is 557 among a set of 6 math glyphs. The following math glyphs have a different width, though:
Width = 556: plus
[code: width-outliers]⚠️ WARN Check font contains no unreachable glyphs
The following glyphs could not be reached by codepoint or substitution rules:
- uni030C.alt
⚠️ WARN Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
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̣̋ ǰ̣ j̣̒ j̦̀ j̦́
Your font fully covers the following languages that require the soft-dotted feature: Dutch (Latn, 31,709,104 speakers), Lithuanian (Latn, 2,357,094 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Avokaya (Latn, 100,000 speakers), Gulay (Latn, 250,478 speakers), Zapotec (Latn, 490,000 speakers), Ngbaka (Latn, 1,020,000 speakers), Belarusian (Cyrl, 10,064,517 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Fur (Latn, 1,230,163 speakers), Sar (Latn, 500,000 speakers), Bete-Bendi (Latn, 100,000 speakers), Igbo (Latn, 27,823,640 speakers), Lugbara (Latn, 2,200,000 speakers), Yala (Latn, 200,000 speakers), Kpelle, Guinea (Latn, 622,000 speakers), Ejagham (Latn, 120,000 speakers), Aghem (Latn, 38,843 speakers), Makaa (Latn, 221,000 speakers), Navajo (Latn, 166,319 speakers), Ijo, Southeast (Latn, 2,471,000 speakers), Mango (Latn, 77,000 speakers), Dii (Latn, 71,000 speakers), Kom (Latn, 360,685 speakers), Cicipu (Latn, 44,000 speakers), Mfumte (Latn, 79,000 speakers), Mundani (Latn, 34,000 speakers), Ma’di (Latn, 584,000 speakers), Dan (Latn, 1,099,244 speakers), Nzakara (Latn, 50,000 speakers), Vute (Latn, 21,000 speakers), South Central Banda (Latn, 244,000 speakers), Ebira (Latn, 2,200,000 speakers), Nateni (Latn, 100,000 speakers), Ekpeye (Latn, 226,000 speakers), Koonzime (Latn, 40,000 speakers), Basaa (Latn, 332,940 speakers), Southern Kisi (Latn, 360,000 speakers), Bafut (Latn, 158,146 speakers).
[code: soft-dotted]⚠️ WARN METADATA.pb: Designers are listed correctly on the Google Fonts catalog?
It seems that Adam Yeo is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry.
[code: profile-not-found]⚠️ WARN Check for codepoints not covered by METADATA subsets.
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, yi
- U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
- U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi
- U+02DB OGONEK: try adding one of: canadian-aboriginal, yi
- U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
- U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, cherokee, coptic, math
- U+0306 COMBINING BREVE: try adding one of: tifinagh, old-permic
- U+0307 COMBINING DOT ABOVE: try adding one of: old-permic, malayalam, canadian-aboriginal, math, tai-le, syriac, tifinagh, coptic
- U+030A COMBINING RING ABOVE: try adding syriac
- U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee 16 more.
Use -F or --full-lists to disable shortening of long lists.
Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu
⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.
This font file does not have a 'meta' table.
[code: lacks-meta-table]ℹ️ INFO Font contains all required tables?
This font contains the following optional tables:
- cvt
- fpgm
- loca
- prep
- GPOS
- GSUB
- gasp
ℹ️ INFO EPAR table present in font?
EPAR table not present in font. To learn more see https://github.com/fonttools/fontbakery/issues/818
[code: lacks-EPAR]ℹ️ INFO Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?
These are the ppm ranges declared on the gasp table:
PPM <= 65535: flag = 0x0F - Use grid-fitting - Use grayscale rendering - Use gridfitting with ClearType symmetric smoothing - Use smoothing along multiple axes with ClearType®
[code: ranges][1] Family checks
Summary
| 💥 ERROR | ☠ FATAL | 🔥 FAIL | ⚠️ WARN | ⏩ SKIP | ℹ️ INFO | ✅ PASS | 🔎 DEBUG |
|---|---|---|---|---|---|---|---|
| 0 | 0 | 10 | 8 | 71 | 7 | 152 | 0 |
| 0% | 0% | 4% | 3% | 29% | 3% | 61% | 0% |
Note: The following loglevels were omitted in this report:
- SKIP
- PASS
- DEBUG
m4rc1e
n8willis
Taken from the upstream repo https://github.com/YADAMSS/Matemasie-Font at commit https://github.com/YADAMSS/Matemasie-Font/commit/f8b28b0ecb71e4556e18b2f4af23ca151243cac0.
PR Checklist: