v1.1
Collecting all updates made for v1.1, from https://github.com/github/hubot-sans/pull/31 and https://github.com/github/hubot-sans/pull/31 primarily.
Hi @eweracs & @tobiasahlin!
Yanone will be off this summer, so it's my time to take a look to the project :)
Like Mona Sans, we will need fonts that follow the GF specs (you can separate them in a folder called googlefonts/ if you want). For now, I exported the fonts with gftools builder config.yaml.
I still see a lot of fails, related to the variable. I think that some of them appear because the masters names are different from the instances. We also need an avar table for the width.
Since I don't see for now any related-design issues, I can do it myself on my fork and send you a PR with the font exported and ready for GF. You can merge these changes in the main branch, I'll fork it then. I just need you confirm if it's ok for you if I change the masters names.
Cheers! ☀️
Here you can find the fontbakery report, I should be able to remove all the fails:
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.
[1] HubotSans-Italic[wdth,wght].ttf
[1] HubotSans[wdth,wght].ttf
All other checks
[27] HubotSans-Italic[wdth,wght].ttf
💥 ERROR Ensure 'ital' STAT axis is boolean value
- 💥 ERROR
Failed with AttributeError: 'NoneType' object has no attribute 'AxisValue'
File "/Users/marichalemma/Google/env/lib/python3.12/site-packages/fontbakery/checkrunner.py", line 213, in _run_check
subresults = list(subresults)
^^^^^^^^^^^^^^^^
File "/Users/marichalemma/Google/env/lib/python3.12/site-packages/fontbakery/checks/opentype/stat.py", line 236, in com_google_fonts_check_italic_axis_in_stat_is_boolean
value, flags, linkedValue = get_STAT_axis_value(ttFont, "ital")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/marichalemma/Google/env/lib/python3.12/site-packages/fontbakery/checks/opentype/stat.py", line 224, in get_STAT_axis_value
for axisValue in font["STAT"].table.AxisValueArray.AxisValue:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[code: failed-check]
🔥 FAIL The variable font 'wdth' (Width) axis coordinate must be 100 on the 'Regular' instance.
- 🔥 FAIL
The "wdth" axis coordinate of the "Regular" instance must be 100. Got 80.0 as a default value instead.
[code: wdth-not-100]
🔥 FAIL STAT table has Axis Value tables?
- 🔥 FAIL
STAT table has no Axis Value tables.
[code: no-axis-value-tables]
🔥 FAIL Ensure dotted circle glyph is present and can attach marks.
- 🔥 FAIL
The following glyphs could not be attached to the dotted circle glyph:
- uni031B
- uni0335
- uni0336
- uni0337
- uni0338
[code: unattached-dotted-circle-marks]
🔥 FAIL Combined length of family and style must not exceed 32 characters.
- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight ExtraLight Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 278 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight ExtraLight Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 278 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Light Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 279 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Light Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 279 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Medium Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 281 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Medium Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 281 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight SemiBold Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 282 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight SemiBold Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 282 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Bold Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 283 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Bold Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 283 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight ExtraBold Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 284 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight ExtraBold Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 284 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Black Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 285 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]- 🔥 FAIL
Variable font instance name 'Hubot Sans ExtraLight Black Italic' formed by space-separated concatenation of font family name (nameID 1) and instance subfamily nameID 285 exceeds 32 characters.
This has been found to cause shaping issues for some accented letters in Microsoft Word on Windows 10 and 11.
[code: instance-too-long]🔥 FAIL Substitute copyright, registered and trademark symbols in name table entries.
- 🔥 FAIL
NAMEID #0 contains symbols that should be replaced by '(c)'.
[code: unwanted-chars]
🔥 FAIL Copyright notices match canonical pattern in fonts
- 🔥 FAIL
Name Table entry: Copyright notices should match a pattern similar to:
"Copyright 2020 The Familyname Project Authors (git url)"
But instead we have got:
"Copyright © 2021 by GitHub.Inc. All rights reserved."
[code: bad-notice-format]🔥 FAIL Validate defaults on fvar table match registered fallback names in GFAxisRegistry.
- 🔥 FAIL
The defaul value wdth:80.0 is not registered as an axis fallback name on the Google Axis Registry. You should consider suggesting the addition of this value to the registry or adopted one of the existing fallback names for this axis: [name: "SuperCondensed" value: 25.0 , name: "UltraCondensed" value: 50.0 , name: "ExtraCondensed" value: 62.5 , name: "Condensed" value: 75.0 , name: "SemiCondensed" value: 87.5 , name: "Normal" value: 100.0 , name: "SemiExpanded" value: 112.5 , name: "Expanded" value: 125.0 , name: "ExtraExpanded" value: 150.0 , name: "UltraExpanded" value: 200.0 ]
[code: not-registered]
🔥 FAIL Are there non-ASCII characters in ASCII-only NAME table entries?
-
🔥 FAIL
Bad string at [nameID 0, 'utf_16_be']: 'b'Copyright © 2021 by GitHub.Inc. All rights reserved.''
[code: bad-string] -
🔥 FAIL
There are 1 strings containing non-ASCII characters in the ASCII-only NAME table entries.
[code: non-ascii-strings]
🔥 FAIL Validate STAT particle names and values match the fallback names in GFAxisRegistry.
- 🔥 FAIL
STAT table is missing Axis Value Records
[code: missing-axis-values]
⚠️ WARN Check accent of Lcaron, dcaron, lcaron, tcaron
-
⚠️ 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]
⚠️ WARN Check font contains no unreachable glyphs
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- iogonek.dotless
- uni1ECB.dotless
[code: unreachable-glyphs]
⚠️ WARN Glyph names are all valid?
- ⚠️ WARN
The following glyph names may be too long for some legacy systems which may expect a maximum 31-characters length limit: periodcentered.loclCAT.case.ss01
[code: legacy-long-names]
⚠️ WARN Are there any misaligned on-curve points?
- ⚠️ WARN
The following glyphs have on-curve points which have potentially incorrect y coordinates:
* uni1EA3 (U+1EA3): X=271.0,Y=727.0 (should be at cap-height 729?)
* aring (U+00E5): X=244.0,Y=730.0 (should be at cap-height 729?)
* uni1EBB (U+1EBB): X=248.0,Y=727.0 (should be at cap-height 729?)
* uni1EC9 (U+1EC9): X=146.0,Y=727.0 (should be at cap-height 729?)
* uni1ECF (U+1ECF): X=258.0,Y=727.0 (should be at cap-height 729?)
* uni1EDF (U+1EDF): X=258.0,Y=727.0 (should be at cap-height 729?)
* germandbls (U+00DF): X=264.5,Y=727.0 (should be at cap-height 729?)
* uni1EE7 (U+1EE7): X=271.0,Y=727.0 (should be at cap-height 729?)
* uni1EED (U+1EED): X=271.0,Y=727.0 (should be at cap-height 729?)
* uring (U+016F): X=244.0,Y=730.0 (should be at cap-height 729?)
* 48 more.
Use -F or --full-lists to disable shortening of long lists.
[code: found-misalignments]⚠️ WARN Check the direction of the outermost contour in each glyph
- ⚠️ WARN
The following glyphs have a counter-clockwise outer contour:
* uni24FF (U+24FF) has a counter-clockwise outer contour
* uni25CF (U+25CF) has a counter-clockwise outer contour
* uni2776 (U+2776) has a counter-clockwise outer contour
* uni2777 (U+2777) has a counter-clockwise outer contour
* uni2778 (U+2778) has a counter-clockwise outer contour
* uni2779 (U+2779) has a counter-clockwise outer contour
* uni277A (U+277A) has a counter-clockwise outer contour
* uni277B (U+277B) has a counter-clockwise outer contour
* uni277C (U+277C) has a counter-clockwise outer contour
* uni277D (U+277D) has a counter-clockwise outer contour
* uni277E (U+277E) has a counter-clockwise outer contour
[code: ccw-outer-contour]
⚠️ WARN Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
- ⚠️ 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̦̊ j̦̋ ǰ̦ j̦̒ į̆ į̇ į̈
Your font fully covers the following languages that require the soft-dotted feature: Lithuanian (Latn, 2,357,094 speakers), Igbo (Latn, 27,823,640 speakers), Dutch (Latn, 31,709,104 speakers), Ebira (Latn, 2,200,000 speakers), Ekpeye (Latn, 226,000 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Mango (Latn, 77,000 speakers), Ejagham (Latn, 120,000 speakers), Gulay (Latn, 250,478 speakers), South Central Banda (Latn, 244,000 speakers), Sar (Latn, 500,000 speakers), Bafut (Latn, 158,146 speakers), Southern Kisi (Latn, 360,000 speakers), Avokaya (Latn, 100,000 speakers), Navajo (Latn, 166,319 speakers), Fur (Latn, 1,230,163 speakers), Kpelle, Guinea (Latn, 622,000 speakers), Makaa (Latn, 221,000 speakers), Lugbara (Latn, 2,200,000 speakers), Bete-Bendi (Latn, 100,000 speakers), Yala (Latn, 200,000 speakers), Nateni (Latn, 100,000 speakers), Ngbaka (Latn, 1,020,000 speakers), Ijo, Southeast (Latn, 2,471,000 speakers), Ma’di (Latn, 584,000 speakers), Mundani (Latn, 34,000 speakers), Zapotec (Latn, 490,000 speakers), Nzakara (Latn, 50,000 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Mfumte (Latn, 79,000 speakers), Kom (Latn, 360,685 speakers), Dii (Latn, 71,000 speakers), Dan (Latn, 1,099,244 speakers), Vute (Latn, 21,000 speakers), Cicipu (Latn, 44,000 speakers), Koonzime (Latn, 40,000 speakers), Aghem (Latn, 38,843 speakers), Belarusian (Cyrl, 10,064,517 speakers), Basaa (Latn, 332,940 speakers).
[code: soft-dotted]⚠️ WARN Check for codepoints not covered by METADATA subsets.
- ⚠️ 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, 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: coptic, tifinagh, cherokee, math
- U+0306 COMBINING BREVE: try adding one of: tifinagh, old-permic
- U+0307 COMBINING DOT ABOVE: try adding one of: tai-le, syriac, coptic, tifinagh, malayalam, old-permic, canadian-aboriginal, math
- U+030A COMBINING RING ABOVE: try adding syriac
- U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee 78 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, vietnamese
⚠️ WARN Is there kerning info for non-ligated sequences?
- ⚠️ WARN
GPOS table lacks kerning info for the following non-ligated sequences:
- f + f
- f + i
- f + l
[code: lacks-kern-info]
⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.
- ⚠️ WARN
This font file does not have a 'meta' table.
[code: lacks-meta-table]
⚠️ WARN Checking OS/2 achVendID.
- ⚠️ WARN
OS/2 VendorID value 'NONE' 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]
ℹ️ INFO Font contains all required tables?
- ℹ️ INFO
This font contains the following optional tables:
- loca
- prep
- GPOS
- GSUB
- gasp
[code: optional-tables]
ℹ️ INFO Check for presence of an ARTICLE.en_us.html file
- ℹ️ INFO
This font doesn't have an ARTICLE.en_us.html file.
[code: missing-article]
ℹ️ INFO EPAR table present in font?
- ℹ️ INFO
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?
- ℹ️ INFO
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][27] HubotSans[wdth,wght].ttf
🔥 FAIL The variable font 'wdth' (Width) axis coordinate must be 100 on the 'Regular' instance.
- 🔥 FAIL
The "wdth" axis coordinate of the "Regular" instance must be 100. Got 80.0 as a default value instead.
[code: wdth-not-100]
🔥 FAIL Validates that when an instance record is included for the default instance, its subfamilyNameID value is set to a name ID whose string is equal to the string of either name ID 2 or 17, and its postScriptNameID value is set to a name ID whose string is equal to the string of name ID 6.
- 🔥 FAIL
'ExtraLight' instance has the same coordinates as the default instance; its subfamily name should be 'ExtraLight Narrow'
[code: invalid-default-instance-subfamily-name]
🔥 FAIL STAT table has Axis Value tables?
-
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table] -
🔥 FAIL
STAT table is missing Axis Value for 'wdth' value '80.0'
[code: missing-axis-value-table]
🔥 FAIL Ensure dotted circle glyph is present and can attach marks.
- 🔥 FAIL
The following glyphs could not be attached to the dotted circle glyph:
- uni031B
- uni0335
- uni0336
- uni0337
- uni0338
[code: unattached-dotted-circle-marks]
🔥 FAIL Substitute copyright, registered and trademark symbols in name table entries.
- 🔥 FAIL
NAMEID #0 contains symbols that should be replaced by '(c)'.
[code: unwanted-chars]
🔥 FAIL Copyright notices match canonical pattern in fonts
- 🔥 FAIL
Name Table entry: Copyright notices should match a pattern similar to:
"Copyright 2020 The Familyname Project Authors (git url)"
But instead we have got:
"Copyright © 2021 by GitHub.Inc. All rights reserved."
[code: bad-notice-format]🔥 FAIL Check font names are correct
- 🔥 FAIL
Font names are incorrect:
| nameID | current | expected |
|---|---|---|
| Family Name | Hubot Sans Variable | Hubot Sans ExtraLight |
| Subfamily Name | Regular | Regular |
| Full Name | Hubot Sans Variable Regular | Hubot Sans ExtraLight |
| Postscript Name | HubotSans-ExtraLightNarrow | HubotSans-ExtraLight |
| Typographic Family Name | Hubot Sans | Hubot Sans |
| Typographic Subfamily Name | ExtraLight Narrow | ExtraLight |
🔥 FAIL Checking OS/2 fsType does not impose restrictions.
- 🔥 FAIL
In this font fsType is set to 8 meaning that: The font may be embedded but must only be installed temporarily on other systems.
No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
[code: drm]🔥 FAIL Validate defaults on fvar table match registered fallback names in GFAxisRegistry.
- 🔥 FAIL
The defaul value wdth:80.0 is not registered as an axis fallback name on the Google Axis Registry. You should consider suggesting the addition of this value to the registry or adopted one of the existing fallback names for this axis: [name: "SuperCondensed" value: 25.0 , name: "UltraCondensed" value: 50.0 , name: "ExtraCondensed" value: 62.5 , name: "Condensed" value: 75.0 , name: "SemiCondensed" value: 87.5 , name: "Normal" value: 100.0 , name: "SemiExpanded" value: 112.5 , name: "Expanded" value: 125.0 , name: "ExtraExpanded" value: 150.0 , name: "UltraExpanded" value: 200.0 ]
[code: not-registered]
🔥 FAIL Are there non-ASCII characters in ASCII-only NAME table entries?
-
🔥 FAIL
Bad string at [nameID 0, 'utf_16_be']: 'b'Copyright © 2021 by GitHub.Inc. All rights reserved.''
[code: bad-string] -
🔥 FAIL
There are 1 strings containing non-ASCII characters in the ASCII-only NAME table entries.
[code: non-ascii-strings]
⚠️ WARN Check accent of Lcaron, dcaron, lcaron, tcaron
-
⚠️ 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]
⚠️ WARN Check font contains no unreachable glyphs
- ⚠️ WARN
The following glyphs could not be reached by codepoint or substitution rules:
- iogonek.dotless
- uni1ECB.dotless
[code: unreachable-glyphs]
⚠️ WARN Glyph names are all valid?
- ⚠️ WARN
The following glyph names may be too long for some legacy systems which may expect a maximum 31-characters length limit: periodcentered.loclCAT.case.ss01
[code: legacy-long-names]
⚠️ WARN Are there any misaligned on-curve points?
- ⚠️ WARN
The following glyphs have on-curve points which have potentially incorrect y coordinates:
* uni1EA3 (U+1EA3): X=179.0,Y=728.0 (should be at cap-height 729?)
* uni1EBB (U+1EBB): X=179.0,Y=728.0 (should be at cap-height 729?)
* uni1EC9 (U+1EC9): X=66.0,Y=728.0 (should be at cap-height 729?)
* uni1ECF (U+1ECF): X=179.0,Y=728.0 (should be at cap-height 729?)
* uni1EDF (U+1EDF): X=179.0,Y=728.0 (should be at cap-height 729?)
* uni1EE7 (U+1EE7): X=193.0,Y=728.0 (should be at cap-height 729?)
* uni1EED (U+1EED): X=193.0,Y=728.0 (should be at cap-height 729?)
* uni1EF7 (U+1EF7): X=164.0,Y=728.0 (should be at cap-height 729?)
* uni1EA3.ss01: X=177.0,Y=728.0 (should be at cap-height 729?)
* six (U+0036): X=160.5,Y=1.5 (should be at baseline 0?)
* 67 more.
Use -F or --full-lists to disable shortening of long lists.
[code: found-misalignments]⚠️ WARN Check the direction of the outermost contour in each glyph
- ⚠️ WARN
The following glyphs have a counter-clockwise outer contour:
* uni24FF (U+24FF) has a counter-clockwise outer contour
* uni25CF (U+25CF) has a counter-clockwise outer contour
* uni2776 (U+2776) has a counter-clockwise outer contour
* uni2777 (U+2777) has a counter-clockwise outer contour
* uni2778 (U+2778) has a counter-clockwise outer contour
* uni2779 (U+2779) has a counter-clockwise outer contour
* uni277A (U+277A) has a counter-clockwise outer contour
* uni277B (U+277B) has a counter-clockwise outer contour
* uni277C (U+277C) has a counter-clockwise outer contour
* uni277D (U+277D) has a counter-clockwise outer contour
* uni277E (U+277E) has a counter-clockwise outer contour
[code: ccw-outer-contour]
⚠️ WARN Ensure soft_dotted characters lose their dot when combined with marks that replace the dot.
- ⚠️ 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̦̊ j̦̋ ǰ̦ j̦̒ į̆ į̇ į̈
Your font fully covers the following languages that require the soft-dotted feature: Lithuanian (Latn, 2,357,094 speakers), Igbo (Latn, 27,823,640 speakers), Dutch (Latn, 31,709,104 speakers), Ebira (Latn, 2,200,000 speakers), Ekpeye (Latn, 226,000 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Mango (Latn, 77,000 speakers), Ejagham (Latn, 120,000 speakers), Gulay (Latn, 250,478 speakers), South Central Banda (Latn, 244,000 speakers), Sar (Latn, 500,000 speakers), Bafut (Latn, 158,146 speakers), Southern Kisi (Latn, 360,000 speakers), Avokaya (Latn, 100,000 speakers), Navajo (Latn, 166,319 speakers), Fur (Latn, 1,230,163 speakers), Kpelle, Guinea (Latn, 622,000 speakers), Makaa (Latn, 221,000 speakers), Lugbara (Latn, 2,200,000 speakers), Bete-Bendi (Latn, 100,000 speakers), Yala (Latn, 200,000 speakers), Nateni (Latn, 100,000 speakers), Ngbaka (Latn, 1,020,000 speakers), Ijo, Southeast (Latn, 2,471,000 speakers), Ma’di (Latn, 584,000 speakers), Mundani (Latn, 34,000 speakers), Zapotec (Latn, 490,000 speakers), Nzakara (Latn, 50,000 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Mfumte (Latn, 79,000 speakers), Kom (Latn, 360,685 speakers), Dii (Latn, 71,000 speakers), Dan (Latn, 1,099,244 speakers), Vute (Latn, 21,000 speakers), Cicipu (Latn, 44,000 speakers), Koonzime (Latn, 40,000 speakers), Aghem (Latn, 38,843 speakers), Belarusian (Cyrl, 10,064,517 speakers), Basaa (Latn, 332,940 speakers).
[code: soft-dotted]⚠️ WARN Check for codepoints not covered by METADATA subsets.
- ⚠️ 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, 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: coptic, tifinagh, cherokee, math
- U+0306 COMBINING BREVE: try adding one of: tifinagh, old-permic
- U+0307 COMBINING DOT ABOVE: try adding one of: tai-le, syriac, coptic, tifinagh, malayalam, old-permic, canadian-aboriginal, math
- U+030A COMBINING RING ABOVE: try adding syriac
- U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee 78 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, vietnamese
⚠️ WARN Is there kerning info for non-ligated sequences?
- ⚠️ WARN
GPOS table lacks kerning info for the following non-ligated sequences:
- f + f
- f + i
- f + l
[code: lacks-kern-info]
⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.
- ⚠️ WARN
This font file does not have a 'meta' table.
[code: lacks-meta-table]
⚠️ WARN Checking OS/2 achVendID.
- ⚠️ WARN
OS/2 VendorID value 'NONE' 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]
ℹ️ INFO Font contains all required tables?
- ℹ️ INFO
This font contains the following optional tables:
- loca
- prep
- GPOS
- GSUB
- gasp
[code: optional-tables]
ℹ️ INFO Check for presence of an ARTICLE.en_us.html file
- ℹ️ INFO
This font doesn't have an ARTICLE.en_us.html file.
[code: missing-article]
ℹ️ INFO EPAR table present in font?
- ℹ️ INFO
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?
- ℹ️ INFO
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][2] Family checks
Summary
| 💥 ERROR | ☠ FATAL | 🔥 FAIL | ⚠️ WARN | ⏩ SKIP | ℹ️ INFO | ✅ PASS | 🔎 DEBUG |
|---|---|---|---|---|---|---|---|
| 1 | 0 | 20 | 22 | 185 | 15 | 235 | 0 |
| 0% | 0% | 4% | 5% | 39% | 3% | 49% | 0% |
Note: The following loglevels were omitted in this report:
- SKIP
- PASS
- DEBUG
Hiii @emmamarichal ! Lovely to meet you, and happy you're joining us to get Hubot Sans up 😌
I'll let @eweracs speak to the details, but as a guiding principle we want to stay consistent with how we set up mona sans - it sounds like your suggested changes are straightforward and aligned with that work, so a PR would be more than welcome ❤️
Excellent! :) I'll try to send you an update next week, I'll let you know both if I meet any trouble!
Could you merge that PR? who is able to merge it?