Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] added #6359

emmamarichal · 2023-06-09T07:59:45Z

2f2040f: [gftools-packager] Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] added

Inclusive Sans Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] taken from the upstream repo https://github.com/LivKing/Inclusive-Sans at commit LivKing/Inclusive-Sans@77fbedf.

c13f643: Description added

To do:

add designer profile
tweet

emmamarichal · 2023-06-09T08:08:42Z

@RosaWagner I corrected this fail: 🔥 FAIL: METADATA.pb: Check URL on copyright string is the same as in repository_url field., but I'm waiting for your review to avoid sending thousand PR to the designer!

RosaWagner · 2023-06-13T10:40:14Z

I saw several issues so I decided to take a deeper look:

The IJ ij glyphs have accents, they should not have accents.
Capital Eszett has a weird design (they could follow this article: https://www.lucasfonts.com/learn/1E9E)
loclMAH is there to give the option to have a proper cedilla instead of a commabelow (otherwise they could just use the non localised L and N with comma below), cf https://forum.glyphsapp.com/t/best-way-to-handle-marshallese-locl-glyphs/10863
They may want to look at this article about ogonek: http://www.twardoch.com/download/polishhowto/ogonek.html
AE ae OE oe digraphs -> each letter should have balanced/equal proportion
periodcentered.loclCAT.case should be centered between the 2 L (as if there were no space), and is a bit low. Better to handle it with negative spacing than with kerning (cause some app don't display kerning by default)
Stylistic sets only have the base glyphs and not the accented ones
Bar of dcroat and hbar should be a bit longer (almost to the middle of the letter), but only a small part outside the stem. Currently the bar of hbar is in the middle of the stem.
Bar of eth should be longer and less vertical
commaaccent should have a similar shape to the actual comma and not a reversed acute (they should not be confused)
Quotedbl and Quotesingle are supposed to be straight
Quoteleft and Quotedblleft are in the wrong direction
registered is often designed as a superscript
macron looks a tiny tiny bit too large (compared to the width of dieresis and tilda), especially on lowercases.
tilda could be confused with macron at small sizes, maybe it could be more curvy to avoid that
there is no bottom anchors in lowercases which leads to weird composites positioning such as in scommaaccent
positioning and size of accents could be more consistent in a general way

emmamarichal · 2023-06-13T12:02:26Z

@RosaWagner ok thanks, I'll write to the designer

emmamarichal · 2023-06-30T10:03:14Z

Updated

Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.32] added

2c9ec4b: [gftools-packager] Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.32] added

Inclusive Sans Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.32] taken from the upstream repo https://github.com/LivKing/Inclusive-Sans at commit LivKing/Inclusive-Sans@9372a18.

d5ee0ef: Description

emmamarichal · 2023-06-30T10:03:31Z

@RosaWagner updated!

RosaWagner · 2023-06-30T11:12:25Z

Sorry I didn't report kerning issues before

….7-5d5b);gftools[0.9.33] added * Inclusive Sans Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] taken from the upstream repo https://github.com/LivKing/Inclusive-Sans at commit LivKing/Inclusive-Sans@97577e1.

emmamarichal · 2023-08-04T07:50:03Z

Updated

Inclusive Sans: Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added

cc5be10: [gftools-packager] Inclusive Sans: Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added

Inclusive Sans Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] taken from the upstream repo https://github.com/LivKing/Inclusive-Sans at commit LivKing/Inclusive-Sans@97577e1.

b7d5f1e: Description

github-actions · 2023-08-04T07:53:43Z

FontBakery report

fontbakery version: 0.9.0a1

[1] Family checks

ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

ℹ INFO From a total of 2 font files, 2 of them (100.00%) lack a STAT table.

And these are the most common STAT axis orderings:
[code: summary]

[19] InclusiveSans-Regular.ttf

💔 ERROR: Familyname must be unique according to namecheck.fontdata.com (com.google.fonts/check/fontdata_namecheck)

💔 ERROR Failed to access: http://namecheck.fontdata.com.
This check relies on the external service http://namecheck.fontdata.com via the internet. While the service cannot be reached or does not respond this check is broken.

  You can exclude this check with the command line option:
  -x com.google.fonts/check/fontdata_namecheck

  Or you can wait until the service is available again.
  If the problem persists please report this issue at: https://github.com/googlefonts/fontbakery/issues

  Original error message:
  <class 'requests.exceptions.ConnectionError'> [code: namecheck-service]

⚠ WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)

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

⚠ WARN: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)

⚠ WARN GF_Latin_Vietnamese is almost fulfilled. Missing codepoints:
- 0x031B (COMBINING HORN)
  [code: missing-codepoints]

⚠ WARN: Check for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)

⚠ 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+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, cherokee, coptic, math
U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh
U+0307 COMBINING DOT ABOVE: try adding one of: coptic, old-permic, canadian-aboriginal, tai-le, syriac, malayalam, tifinagh, math
U+030A COMBINING RING ABOVE: try adding syriac
U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee
U+030C COMBINING CARON: try adding one of: cherokee, tai-le
U+0331 COMBINING MACRON BELOW: try adding one of: gothic, syriac, cherokee, caucasian-albanian, tifinagh

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu, vietnamese [code: unreachable-subsetting]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts (com.google.fonts/check/repo/vf_has_static_fonts)

⚠ WARN Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

⚠ WARN: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)

⚠ WARN It seems that Olivia King 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: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

⚠ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]

⚠ WARN: Check if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)

⚠ 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: aogonek	Contours detected: 3	Expected: 2

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

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

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

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

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

[code: contour-count]

⚠ WARN: Are any segments inordinately short? (com.google.fonts/check/outline_short_segments)

⚠ WARN The following glyphs have segments which seem very short:
- dollar (U+0024) contains a short segment L<<289.0,317.0>--<286.0,317.0>>
- ampersand (U+0026) contains a short segment L<<624.0,0.0>--<608.0,0.0>>
- sterling (U+00A3) contains a short segment L<<247.0,281.0>--<247.0,278.0>>
- germandbls (U+00DF) contains a short segment B<<249.0,70.0>-<257.0,69.0>-<267.0,68.5>>
- germandbls (U+00DF) contains a short segment B<<267.0,68.5>-<277.0,68.0>-<288.0,68.0>>
- germandbls (U+00DF) contains a short segment L<<283.0,418.0>--<287.0,418.0>>
- ae (U+00E6) contains a short segment B<<145.5,368.0>-<139.0,356.0>-<139.0,356.0>>
- ae (U+00E6) contains a short segment B<<71.0,393.0>-<71.0,393.0>-<80.5,411.0>>
- uni0123 (U+0123) contains a short segment B<<278.5,664.0>-<281.0,664.0>-<282.0,664.0>>
- Eng (U+014A) contains a short segment B<<462.0,-188.0>-<450.0,-188.0>-<434.5,-186.0>>
- 25 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

⚠ WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)

⚠ WARN The following glyphs have colinear vectors:
- OE (U+0152): L<<677.0,400.0>--<677.0,400.0>> -> L<<677.0,400.0>--<950.0,400.0>> [code: found-colinear-vectors]

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

⚠ WARN The following glyphs have jaggy segments:
- nine (U+0039): L<<201.0,0.0>--<375.0,273.0>>/B<<375.0,273.0>-<366.0,262.0>-<342.5,255.0>> = 6.777492631448893
- six (U+0036): L<<410.0,700.0>--<236.0,427.0>>/B<<236.0,427.0>-<245.0,438.0>-<268.5,445.0>> = 6.777492631448839
- u (U+0075): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- uacute (U+00FA): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- ubreve (U+016D): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- ucircumflex (U+00FB): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- udieresis (U+00FC): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- ugrave (U+00F9): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- uhorn (U+01B0): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- uhungarumlaut (U+0171): L<<421.0,0.0>--<421.0,94.0>>/B<<421.0,94.0>-<417.0,77.0>-<398.5,51.5>> = 13.240519915187184
- 11 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-jaggy-segments]

⚠ WARN: Ensure dotted circle glyph is present and can attach marks. (com.google.fonts/check/dotted_circle)

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

ℹ INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)

ℹ INFO Found a git repo URL: https://github.com/LivKing/Inclusive-Sans [code: url-found]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

ℹ INFO Hinting filesize impact:

	ofl/inclusivesans/InclusiveSans-Regular.ttf
Dehinted Size	38.4kb
Hinted Size	56.0kb
Increase	17.7kb
Change	46.0 %
[code: size-impact]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

ℹ INFO EPAR table not present in font. To learn more see When missing EPAR table, just emit INFO alert fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

ℹ 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]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

ℹ INFO Version string is: "Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33]"
The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
"Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

ℹ INFO This font contains the following optional tables:
- cvt
- fpgm
- loca
- prep
- GPOS
- GSUB
- gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

ℹ INFO ofl/inclusivesans [code: family-path]

[19] InclusiveSans-Italic.ttf

💔 ERROR: Familyname must be unique according to namecheck.fontdata.com (com.google.fonts/check/fontdata_namecheck)

💔 ERROR Failed to access: http://namecheck.fontdata.com.
This check relies on the external service http://namecheck.fontdata.com via the internet. While the service cannot be reached or does not respond this check is broken.

  You can exclude this check with the command line option:
  -x com.google.fonts/check/fontdata_namecheck

  Or you can wait until the service is available again.
  If the problem persists please report this issue at: https://github.com/googlefonts/fontbakery/issues

  Original error message:
  <class 'requests.exceptions.ConnectionError'> [code: namecheck-service]

⚠ WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)

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

⚠ WARN: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)

⚠ WARN GF_Latin_Vietnamese is almost fulfilled. Missing codepoints:
- 0x031B (COMBINING HORN)
  [code: missing-codepoints]

⚠ WARN: Check for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)

⚠ 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+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, cherokee, coptic, math
U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh
U+0307 COMBINING DOT ABOVE: try adding one of: coptic, old-permic, canadian-aboriginal, tai-le, syriac, malayalam, tifinagh, math
U+030A COMBINING RING ABOVE: try adding syriac
U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee
U+030C COMBINING CARON: try adding one of: cherokee, tai-le
U+0331 COMBINING MACRON BELOW: try adding one of: gothic, syriac, cherokee, caucasian-albanian, tifinagh

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu, vietnamese [code: unreachable-subsetting]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts (com.google.fonts/check/repo/vf_has_static_fonts)

⚠ WARN Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

⚠ WARN: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)

⚠ WARN It seems that Olivia King 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: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

⚠ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]

⚠ WARN: Check if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)

⚠ 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: aogonek	Contours detected: 3	Expected: 2

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

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

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

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

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

[code: contour-count]

⚠ WARN: Are any segments inordinately short? (com.google.fonts/check/outline_short_segments)

⚠ WARN The following glyphs have segments which seem very short:
- dollar (U+0024) contains a short segment L<<298.0,316.0>--<295.0,317.0>>
- ampersand (U+0026) contains a short segment L<<589.0,0.0>--<573.0,0.0>>
- at (U+0040) contains a short segment B<<664.5,164.5>-<679.0,149.0>-<698.0,149.0>>
- sterling (U+00A3) contains a short segment L<<251.0,281.0>--<251.0,278.0>>
- Thorn (U+00DE) contains a short segment L<<125.0,464.0>--<125.0,464.0>>
- Thorn (U+00DE) contains a short segment L<<213.0,464.0>--<213.0,464.0>>
- germandbls (U+00DF) contains a short segment B<<224.0,70.0>-<232.0,69.0>-<241.5,68.5>>
- germandbls (U+00DF) contains a short segment B<<241.5,68.5>-<251.0,68.0>-<262.0,68.0>>
- germandbls (U+00DF) contains a short segment L<<307.0,418.0>--<311.0,418.0>>
- ae (U+00E6) contains a short segment B<<162.0,368.0>-<154.0,356.0>-<154.0,356.0>>
- 22 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

⚠ WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)

⚠ WARN The following glyphs have colinear vectors:
- Ohorn (U+01A0): L<<366.0,713.0>--<372.0,713.0>> -> L<<372.0,713.0>--<372.0,713.0>>
- uni1EDA (U+1EDA): L<<366.0,713.0>--<372.0,713.0>> -> L<<372.0,713.0>--<372.0,713.0>>
- uni1EDC (U+1EDC): L<<366.0,713.0>--<372.0,713.0>> -> L<<372.0,713.0>--<372.0,713.0>>
- uni1EDE (U+1EDE): L<<366.0,713.0>--<372.0,713.0>> -> L<<372.0,713.0>--<372.0,713.0>>
- uni1EE0 (U+1EE0): L<<366.0,713.0>--<372.0,713.0>> -> L<<372.0,713.0>--<372.0,713.0>>
- uni1EE2 (U+1EE2): L<<366.0,713.0>--<372.0,713.0>> -> L<<372.0,713.0>--<372.0,713.0>> [code: found-colinear-vectors]

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

⚠ WARN The following glyphs have jaggy segments:
- eng (U+014B): L<<211.0,500.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.376567375407593
- h (U+0068): L<<241.0,712.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.251514547724467
- hbar (U+0127): L<<260.0,582.0>--<235.0,406.0>>/B<<235.0,406.0>-<242.0,424.0>-<263.5,449.0>> = 13.165984511311175
- m (U+006D): B<<475.5,482.5>-<514.0,453.0>-<523.0,396.0>>/L<<523.0,396.0>--<523.0,398.0>> = 8.972626614896399
- m (U+006D): L<<211.0,500.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.376567375407593
- n (U+006E): L<<211.0,500.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.376567375407593
- nacute (U+0144): L<<211.0,500.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.376567375407593
- ncaron (U+0148): L<<211.0,500.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.376567375407593
- nine (U+0039): L<<166.0,0.0>--<378.0,273.0>>/B<<378.0,273.0>-<368.0,262.0>-<343.5,255.0>> = 4.442320504789463
- nmacronbelow (U+1E49): L<<211.0,500.0>--<198.0,406.0>>/B<<198.0,406.0>-<205.0,424.0>-<226.5,449.0>> = 13.376567375407593
- 6 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-jaggy-segments]

⚠ WARN: Ensure dotted circle glyph is present and can attach marks. (com.google.fonts/check/dotted_circle)

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

ℹ INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)

ℹ INFO Found a git repo URL: https://github.com/LivKing/Inclusive-Sans [code: url-found]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

ℹ INFO Hinting filesize impact:

	ofl/inclusivesans/InclusiveSans-Italic.ttf
Dehinted Size	40.1kb
Hinted Size	57.5kb
Increase	17.4kb
Change	43.4 %
[code: size-impact]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

ℹ INFO EPAR table not present in font. To learn more see When missing EPAR table, just emit INFO alert fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

ℹ 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]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

ℹ INFO Version string is: "Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33]"
The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
"Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

ℹ INFO This font contains the following optional tables:
- cvt
- fpgm
- loca
- prep
- GPOS
- GSUB
- gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

ℹ INFO ofl/inclusivesans [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
2	0	22	130	15	308	0
0%	0%	5%	27%	3%	65%	0%

Note: The following loglevels were omitted in this report:

SKIP
PASS
DEBUG

emmamarichal added - Ready for Review I New Font labels Jun 9, 2023

emmamarichal linked an issue Jun 9, 2023 that may be closed by this pull request

Add Inclusive Sans #5728

Closed

9 tasks

This comment was marked as outdated.

Sign in to view

RosaWagner added -- Needs Upstream Resolution Upstream fix required before moving forward and removed - Ready for Review labels Jun 13, 2023

emmamarichal mentioned this pull request Jun 28, 2023

Designer added: Olivia King #6471

Merged

emmamarichal force-pushed the gftools_packager_ofl_inclusivesans branch from c13f643 to d5ee0ef Compare June 30, 2023 10:03

emmamarichal removed the -- Needs Upstream Resolution Upstream fix required before moving forward label Jun 30, 2023

This comment was marked as outdated.

Sign in to view

emmamarichal added the -- Needs Upstream Resolution Upstream fix required before moving forward label Jul 5, 2023

emmamarichal added 2 commits August 4, 2023 09:48

Description

b7d5f1e

emmamarichal force-pushed the gftools_packager_ofl_inclusivesans branch from d5ee0ef to b7d5f1e Compare August 4, 2023 07:50

emmamarichal removed the -- Needs Upstream Resolution Upstream fix required before moving forward label Aug 4, 2023

RosaWagner self-requested a review August 29, 2023 12:18

RosaWagner approved these changes Aug 29, 2023

View reviewed changes

RosaWagner merged commit c3a12fb into main Aug 29, 2023
9 checks passed

RosaWagner deleted the gftools_packager_ofl_inclusivesans branch August 29, 2023 12:18

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] added #6359

Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] added #6359

emmamarichal commented Jun 9, 2023 •

edited

Loading

This comment was marked as outdated.

emmamarichal commented Jun 9, 2023

RosaWagner commented Jun 13, 2023

emmamarichal commented Jun 13, 2023

emmamarichal commented Jun 30, 2023

emmamarichal commented Jun 30, 2023

This comment was marked as outdated.

RosaWagner commented Jun 30, 2023

emmamarichal commented Aug 4, 2023

github-actions bot commented Aug 4, 2023

Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] added #6359

Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.30] added #6359

Conversation

emmamarichal commented Jun 9, 2023 • edited Loading

This comment was marked as outdated.

emmamarichal commented Jun 9, 2023

RosaWagner commented Jun 13, 2023

emmamarichal commented Jun 13, 2023

emmamarichal commented Jun 30, 2023

Inclusive Sans: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.32] added

emmamarichal commented Jun 30, 2023

This comment was marked as outdated.

RosaWagner commented Jun 30, 2023

emmamarichal commented Aug 4, 2023

Inclusive Sans: Version 1.001; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added

github-actions bot commented Aug 4, 2023

FontBakery report

Summary

emmamarichal commented Jun 9, 2023 •

edited

Loading