Bungee Tint: Version 2.001 added

[vv-monsalve]

Taken from the upstream repo https://github.com/djrrb/Bungee at commit djrrb/Bungee@0ab742e.

PR Checklist:

• Family categorization tags collected from the type design team with the Categories Form
• minisite_url definition in the METADATA.pb file for commissioned projects
• primary_script definition in the METADATA.pb file for all projects that have a primary non-Latin based language support target
• subsets definitions in the METADATA.pb reflect the actual subsets and languages present in the font files (in alphabetic order)
• Fontbakery checks are reviewed and failing checks are resolved in collaboration with the upstream font development team
• Diffenator2 regression checks for revisions on all projects that are currently in production
• Designers bio info have to be present in the designer catalog (at least an issue should be opened for tracking this, if they are not)
• Check designers order in metadata.pb, since the first one of the list appears as “principal designer”
• Social media formatted visual assets for all new commissioned projects in the Drive directory, communicate with the repository Maintainer so that they can push this content to the Social Media tracker spreadsheet
• Social media content draft for all new commissioned projects in the Drive directory and Social Media tracker spreadsheet, communicate with the repository Maintainer so that they can push this content to the Social Media tracker spreadsheet

[github-actions]

FontBakery report

fontbakery version: 0.12.9

Experimental checks

These won't break the CI job for now, but will become effective after some time if nobody raises any concern.

[1] BungeeTint-Regular.ttf

🔥 FAIL Validate size, and resolution of article images, and ensure article page has minimum length and includes visual assets.

• 🔥 FAIL

  Image is too large: 2048 x 1247 pixels

Max resolution allowed: 2048 x 1024 pixels

[code: image-too-large]

• 🔥 FAIL

  Image is too large: 2239 x 1793 pixels

Max resolution allowed: 2048 x 1024 pixels

[code: image-too-large]

• 🔥 FAIL

  Image is too large: 1925 x 1585 pixels

Max resolution allowed: 2048 x 1024 pixels

[code: image-too-large]

• 🔥 FAIL

  Image is too large: 2048 x 1331 pixels

Max resolution allowed: 2048 x 1024 pixels

[code: image-too-large]

All other checks

[20] BungeeTint-Regular.ttf

🔥 FAIL Check accent of Lcaron, dcaron, lcaron, tcaron

• 🔥 FAIL

  dcaron uses component caroncmb.

  
  [code: wrong-mark]

• 🔥 FAIL

  tcaron uses component caroncmb.

  
  [code: wrong-mark]

• ⚠️ WARN

  Lcaron is decomposed and therefore could not be checked. Please check manually.

  
  [code: decomposed-outline]

• ⚠️ WARN

  lcaron is composed of a single component and therefore could not be checked. Please check manually.

  
  [code: single-component]

🔥 FAIL Does DESCRIPTION file contain broken links?

• 🔥 FAIL

  The following links are broken in the article file:
  https://fontbureau.com (status code: 404)

  
  [code: broken-links]

⚠️ WARN Check glyphs in mark glyph class are non-spacing.

• ⚠️ WARN

  The following spacing glyphs may be in the GDEF mark glyph class by mistake:
  commaaccent (U+0326), commaaccent (U+F6C3) and commaaccent.inline (unencoded)

  
  [code: spacing-mark-glyphs]

⚠️ WARN Check mark characters are in GDEF mark glyph class.

• ⚠️ WARN

  The following mark characters could be in the GDEF mark glyph class:
  horncmb (U+031B)

  
  [code: mark-chars]

⚠️ WARN Check if each glyph has the recommended amount of contours.

• ⚠️ 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: aring	Contours detected: 3	Expected: 4


Glyph name: ae	Contours detected: 2	Expected: 3


Glyph name: egrave	Contours detected: 2	Expected: 3


Glyph name: eacute	Contours detected: 2	Expected: 3


65 more.

Use -F or --full-lists to disable shortening of long lists.

[code: contour-count]

⚠️ WARN Check math signs have the same width.

• ⚠️ WARN

  The most common width is 734 among a set of 9 math glyphs.
  The following math glyphs have a different width, though:

Width = 714: less, greater, lessequal, greaterequal

[code: width-outliers]

⚠️ 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:
  blackdownpointingtriangle.inline, blackleftpointingtriangle.inline, blackrightpointingtriangle.inline, indexdownleft.salt_outline.inline, indexdownright.salt_outline.inline, indexupright.salt_outline.inline, whitedownpointingtriangle.inline, whiteleftpointingtriangle.inline and whiterightpointingtriangle.inline

  
  [code: legacy-long-names]

⚠️ WARN Do outlines contain any jaggy segments?

• ⚠️ WARN

  The following glyphs have jaggy segments:

* indexdownleft.outline (U+E142): L<<538.0,163.0>--<475.0,110.0>>/L<<475.0,110.0>--<477.0,111.0>> = 13.50783887527299

* indexdownright.outline (U+E143): L<<523.0,111.0>--<525.0,110.0>>/L<<525.0,110.0>--<462.0,163.0>> = 13.50783887527299

* indexupleft.outline (U+E144): L<<303.0,322.0>--<250.0,385.0>>/L<<250.0,385.0>--<251.0,383.0>> = 13.50783887527299

* indexupright.outline (U+E145): L<<749.0,383.0>--<750.0,385.0>>/L<<750.0,385.0>--<697.0,322.0>> = 13.50783887527299

* indianrupee.inline: B<<366.5,320.5>-<354.0,291.0>-<316.0,280.0>>/L<<316.0,280.0>--<340.0,281.0>> = 13.758394749894615

* indianrupee.inline: L<<129.0,272.0>--<176.0,274.0>>/L<<176.0,274.0>--<129.0,274.0>> = 2.436648246810141

* indianrupee.inline: L<<340.0,272.0>--<129.0,272.0>>/L<<129.0,272.0>--<176.0,274.0>> = 2.436648246810141

* onethird.inline: B<<997.5,291.0>-<990.0,271.0>-<957.0,264.0>>/L<<957.0,264.0>--<968.0,264.0>> = 11.976132444203333

* three.inline: B<<402.0,388.5>-<388.0,374.0>-<358.0,367.0>>/L<<358.0,367.0>--<374.0,367.0>> = 13.134022306396327

* three.sinf.inline: B<<312.5,291.0>-<305.0,271.0>-<272.0,264.0>>/L<<272.0,264.0>--<283.0,264.0>> = 11.976132444203333

* 7 more.

Use -F or --full-lists to disable shortening of long lists.

[code: found-jaggy-segments]

⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines?

• ⚠️ WARN

  The following glyphs have semi-vertical/semi-horizontal lines:

* M.v (U+FF4D): L<<179.0,36.0>--<183.0,684.0>>

* M.v (U+FF4D): L<<819.0,684.0>--<823.0,36.0>>

* M.v.inline: L<<277.0,90.0>--<279.0,599.0>>

* M.v.inline: L<<289.0,599.0>--<287.0,90.0>>

* M.v.inline: L<<705.0,90.0>--<703.0,599.0>>

* M.v.inline: L<<713.0,599.0>--<715.0,90.0>>

* asciicircum (U+005E): L<<202.0,171.0>--<70.0,172.0>>

* asciicircum (U+005E): L<<609.0,172.0>--<477.0,171.0>>

* ascript (U+0251): L<<675.0,530.0>--<677.0,36.0>>

[code: found-semi-vertical]

⚠️ WARN Ensure dotted circle glyph is present and can attach marks.

• ⚠️ WARN

  No dotted circle glyph present

  
  [code: missing-dotted-circle]

⚠️ 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+02BE MODIFIER LETTER RIGHT HALF RING: not included in any glyphset definition
• U+02BF MODIFIER LETTER LEFT HALF RING: not included in any glyphset definition
• U+02C7 CARON: try adding one of: canadian-aboriginal, yi, tifinagh
• U+02C8 MODIFIER LETTER VERTICAL LINE: not included in any glyphset definition
• U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
• U+02CA MODIFIER LETTER ACUTE ACCENT: not included in any glyphset definition
• U+02CB MODIFIER LETTER GRAVE ACCENT: not included in any glyphset definition
• U+02CC MODIFIER LETTER LOW VERTICAL LINE: not included in any glyphset definition
• U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
• U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi 535 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, vietnamese

[code: unreachable-subsetting]

⚠️ WARN Is there kerning info for non-ligated sequences?

• ⚠️ WARN

  GPOS table lacks kerning info for the following non-ligated sequences:

- I.salt_v + I.salt_v

[code: lacks-kern-info]

⚠️ WARN Are there caret positions declared for every ligature?

• ⚠️ WARN

  This font lacks caret position values for ligature glyphs on its GDEF table.

  
  [code: lacks-caret-pos]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.

• ⚠️ WARN

  This font file does not have a 'meta' table.

  
  [code: lacks-meta-table]

ℹ️ INFO List all superfamily filepaths

• ℹ️ INFO

  ofl/bungeetint

  
  [code: family-path]

ℹ️ INFO Font contains all required tables?

• ℹ️ INFO

  This font contains the following optional tables:

- loca

- prep

- GPOS

- GSUB

- gasp

- vhea

- vmtx

[code: optional-tables]

ℹ️ INFO EPAR table present in font?

• ℹ️ 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?

• ℹ️ 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 Show hinting filesize impact.

• ℹ️ INFO

  Hinting filesize impact:

	ofl/bungeetint/BungeeTint-Regular.ttf
Dehinted Size	216.6kb
Hinted Size	216.7kb
Increase	24 bytes
Change	0.0 %

[code: size-impact]

ℹ️ INFO Font has old ttfautohint applied?

• ℹ️ INFO

  Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 2.001']

  
  [code: version-not-detected]

[1] Family checks

ℹ️ INFO Check axis ordering on the STAT table.

• ℹ️ INFO

  All of the fonts lack a STAT table.

  
  [code: summary]

Summary

💥 ERROR	☠ FATAL	🔥 FAIL	⚠️ WARN	⏩ SKIP	ℹ️ INFO	✅ PASS	🔎 DEBUG
0	0	3	12	70	7	160	0
0%	0%	1%	5%	28%	3%	63%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[github-actions]

FontBakery report

fontbakery version: 0.12.9

Experimental checks

These won't break the CI job for now, but will become effective after some time if nobody raises any concern.

[1] BungeeTint-Regular.ttf

🔥 FAIL Validate size, and resolution of article images, and ensure article page has minimum length and includes visual assets.

• 🔥 FAIL

  Image is too large: 1280 x 1025 pixels

Max resolution allowed: 2048 x 1024 pixels

[code: image-too-large]

All other checks

[20] BungeeTint-Regular.ttf

🔥 FAIL Check accent of Lcaron, dcaron, lcaron, tcaron

• 🔥 FAIL

  dcaron uses component caroncmb.

  
  [code: wrong-mark]

• 🔥 FAIL

  tcaron uses component caroncmb.

  
  [code: wrong-mark]

• ⚠️ WARN

  Lcaron is decomposed and therefore could not be checked. Please check manually.

  
  [code: decomposed-outline]

• ⚠️ WARN

  lcaron is composed of a single component and therefore could not be checked. Please check manually.

  
  [code: single-component]

🔥 FAIL Does DESCRIPTION file contain broken links?

• 🔥 FAIL

  The following links are broken in the article file:
  https://fontbureau.com (status code: 404)

  
  [code: broken-links]

⚠️ WARN Check glyphs in mark glyph class are non-spacing.

• ⚠️ WARN

  The following spacing glyphs may be in the GDEF mark glyph class by mistake:
  commaaccent (U+0326), commaaccent (U+F6C3) and commaaccent.inline (unencoded)

  
  [code: spacing-mark-glyphs]

⚠️ WARN Check mark characters are in GDEF mark glyph class.

• ⚠️ WARN

  The following mark characters could be in the GDEF mark glyph class:
  horncmb (U+031B)

  
  [code: mark-chars]

⚠️ WARN Check if each glyph has the recommended amount of contours.

• ⚠️ 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: aring	Contours detected: 3	Expected: 4


Glyph name: ae	Contours detected: 2	Expected: 3


Glyph name: egrave	Contours detected: 2	Expected: 3


Glyph name: eacute	Contours detected: 2	Expected: 3


65 more.

Use -F or --full-lists to disable shortening of long lists.

[code: contour-count]

⚠️ WARN Check math signs have the same width.

• ⚠️ WARN

  The most common width is 734 among a set of 9 math glyphs.
  The following math glyphs have a different width, though:

Width = 714: greaterequal, less, lessequal, greater

[code: width-outliers]

⚠️ 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:
  blackdownpointingtriangle.inline, blackleftpointingtriangle.inline, blackrightpointingtriangle.inline, indexdownleft.salt_outline.inline, indexdownright.salt_outline.inline, indexupright.salt_outline.inline, whitedownpointingtriangle.inline, whiteleftpointingtriangle.inline and whiterightpointingtriangle.inline

  
  [code: legacy-long-names]

⚠️ WARN Do outlines contain any jaggy segments?

• ⚠️ WARN

  The following glyphs have jaggy segments:

* indexdownleft.outline (U+E142): L<<538.0,163.0>--<475.0,110.0>>/L<<475.0,110.0>--<477.0,111.0>> = 13.50783887527299

* indexdownright.outline (U+E143): L<<523.0,111.0>--<525.0,110.0>>/L<<525.0,110.0>--<462.0,163.0>> = 13.50783887527299

* indexupleft.outline (U+E144): L<<303.0,322.0>--<250.0,385.0>>/L<<250.0,385.0>--<251.0,383.0>> = 13.50783887527299

* indexupright.outline (U+E145): L<<749.0,383.0>--<750.0,385.0>>/L<<750.0,385.0>--<697.0,322.0>> = 13.50783887527299

* indianrupee.inline: B<<366.5,320.5>-<354.0,291.0>-<316.0,280.0>>/L<<316.0,280.0>--<340.0,281.0>> = 13.758394749894615

* indianrupee.inline: L<<129.0,272.0>--<176.0,274.0>>/L<<176.0,274.0>--<129.0,274.0>> = 2.436648246810141

* indianrupee.inline: L<<340.0,272.0>--<129.0,272.0>>/L<<129.0,272.0>--<176.0,274.0>> = 2.436648246810141

* onethird.inline: B<<997.5,291.0>-<990.0,271.0>-<957.0,264.0>>/L<<957.0,264.0>--<968.0,264.0>> = 11.976132444203333

* three.inline: B<<402.0,388.5>-<388.0,374.0>-<358.0,367.0>>/L<<358.0,367.0>--<374.0,367.0>> = 13.134022306396327

* three.sinf.inline: B<<312.5,291.0>-<305.0,271.0>-<272.0,264.0>>/L<<272.0,264.0>--<283.0,264.0>> = 11.976132444203333

* 7 more.

Use -F or --full-lists to disable shortening of long lists.

[code: found-jaggy-segments]

⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines?

• ⚠️ WARN

  The following glyphs have semi-vertical/semi-horizontal lines:

* M.v (U+FF4D): L<<179.0,36.0>--<183.0,684.0>>

* M.v (U+FF4D): L<<819.0,684.0>--<823.0,36.0>>

* M.v.inline: L<<277.0,90.0>--<279.0,599.0>>

* M.v.inline: L<<289.0,599.0>--<287.0,90.0>>

* M.v.inline: L<<705.0,90.0>--<703.0,599.0>>

* M.v.inline: L<<713.0,599.0>--<715.0,90.0>>

* asciicircum (U+005E): L<<202.0,171.0>--<70.0,172.0>>

* asciicircum (U+005E): L<<609.0,172.0>--<477.0,171.0>>

* ascript (U+0251): L<<675.0,530.0>--<677.0,36.0>>

[code: found-semi-vertical]

⚠️ WARN Ensure dotted circle glyph is present and can attach marks.

• ⚠️ WARN

  No dotted circle glyph present

  
  [code: missing-dotted-circle]

⚠️ 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+02BE MODIFIER LETTER RIGHT HALF RING: not included in any glyphset definition
• U+02BF MODIFIER LETTER LEFT HALF RING: not included in any glyphset definition
• U+02C7 CARON: try adding one of: canadian-aboriginal, yi, tifinagh
• U+02C8 MODIFIER LETTER VERTICAL LINE: not included in any glyphset definition
• U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
• U+02CA MODIFIER LETTER ACUTE ACCENT: not included in any glyphset definition
• U+02CB MODIFIER LETTER GRAVE ACCENT: not included in any glyphset definition
• U+02CC MODIFIER LETTER LOW VERTICAL LINE: not included in any glyphset definition
• U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
• U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi 535 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, vietnamese

[code: unreachable-subsetting]

⚠️ WARN Is there kerning info for non-ligated sequences?

• ⚠️ WARN

  GPOS table lacks kerning info for the following non-ligated sequences:

- I.salt_v + I.salt_v

[code: lacks-kern-info]

⚠️ WARN Are there caret positions declared for every ligature?

• ⚠️ WARN

  This font lacks caret position values for ligature glyphs on its GDEF table.

  
  [code: lacks-caret-pos]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.

• ⚠️ WARN

  This font file does not have a 'meta' table.

  
  [code: lacks-meta-table]

ℹ️ INFO List all superfamily filepaths

• ℹ️ INFO

  ofl/bungeetint

  
  [code: family-path]

ℹ️ INFO Font contains all required tables?

• ℹ️ INFO

  This font contains the following optional tables:

- loca

- prep

- GPOS

- GSUB

- gasp

- vhea

- vmtx

[code: optional-tables]

ℹ️ INFO EPAR table present in font?

• ℹ️ 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?

• ℹ️ 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 Show hinting filesize impact.

• ℹ️ INFO

  Hinting filesize impact:

	ofl/bungeetint/BungeeTint-Regular.ttf
Dehinted Size	216.6kb
Hinted Size	216.7kb
Increase	24 bytes
Change	0.0 %

[code: size-impact]

ℹ️ INFO Font has old ttfautohint applied?

• ℹ️ INFO

  Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 2.001']

  
  [code: version-not-detected]

[1] Family checks

ℹ️ INFO Check axis ordering on the STAT table.

• ℹ️ INFO

  All of the fonts lack a STAT table.

  
  [code: summary]

Summary

💥 ERROR	☠ FATAL	🔥 FAIL	⚠️ WARN	⏩ SKIP	ℹ️ INFO	✅ PASS	🔎 DEBUG
0	0	3	12	70	7	160	0
0%	0%	1%	5%	28%	3%	63%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[github-actions]

FontBakery report

fontbakery version: 0.12.9

Check results

[20] BungeeTint-Regular.ttf

🔥 FAIL Check accent of Lcaron, dcaron, lcaron, tcaron

• 🔥 FAIL

  dcaron uses component caroncmb.

  
  [code: wrong-mark]

• 🔥 FAIL

  tcaron uses component caroncmb.

  
  [code: wrong-mark]

• ⚠️ WARN

  Lcaron is decomposed and therefore could not be checked. Please check manually.

  
  [code: decomposed-outline]

• ⚠️ WARN

  lcaron is composed of a single component and therefore could not be checked. Please check manually.

  
  [code: single-component]

🔥 FAIL Does DESCRIPTION file contain broken links?

• 🔥 FAIL

  The following links are broken in the article file:
  https://fontbureau.com (status code: 404)

  
  [code: broken-links]

⚠️ WARN Check glyphs in mark glyph class are non-spacing.

• ⚠️ WARN

  The following spacing glyphs may be in the GDEF mark glyph class by mistake:
  commaaccent (U+0326), commaaccent (U+F6C3) and commaaccent.inline (unencoded)

  
  [code: spacing-mark-glyphs]

⚠️ WARN Check mark characters are in GDEF mark glyph class.

• ⚠️ WARN

  The following mark characters could be in the GDEF mark glyph class:
  horncmb (U+031B)

  
  [code: mark-chars]

⚠️ WARN Check if each glyph has the recommended amount of contours.

• ⚠️ 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: aring	Contours detected: 3	Expected: 4


Glyph name: ae	Contours detected: 2	Expected: 3


Glyph name: egrave	Contours detected: 2	Expected: 3


Glyph name: eacute	Contours detected: 2	Expected: 3


65 more.

Use -F or --full-lists to disable shortening of long lists.

[code: contour-count]

⚠️ WARN Check math signs have the same width.

• ⚠️ WARN

  The most common width is 734 among a set of 9 math glyphs.
  The following math glyphs have a different width, though:

Width = 714: less, lessequal, greater, greaterequal

[code: width-outliers]

⚠️ 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:
  blackdownpointingtriangle.inline, blackleftpointingtriangle.inline, blackrightpointingtriangle.inline, indexdownleft.salt_outline.inline, indexdownright.salt_outline.inline, indexupright.salt_outline.inline, whitedownpointingtriangle.inline, whiteleftpointingtriangle.inline and whiterightpointingtriangle.inline

  
  [code: legacy-long-names]

⚠️ WARN Do outlines contain any jaggy segments?

• ⚠️ WARN

  The following glyphs have jaggy segments:

* indexdownleft.outline (U+E142): L<<538.0,163.0>--<475.0,110.0>>/L<<475.0,110.0>--<477.0,111.0>> = 13.50783887527299

* indexdownright.outline (U+E143): L<<523.0,111.0>--<525.0,110.0>>/L<<525.0,110.0>--<462.0,163.0>> = 13.50783887527299

* indexupleft.outline (U+E144): L<<303.0,322.0>--<250.0,385.0>>/L<<250.0,385.0>--<251.0,383.0>> = 13.50783887527299

* indexupright.outline (U+E145): L<<749.0,383.0>--<750.0,385.0>>/L<<750.0,385.0>--<697.0,322.0>> = 13.50783887527299

* indianrupee.inline: B<<366.5,320.5>-<354.0,291.0>-<316.0,280.0>>/L<<316.0,280.0>--<340.0,281.0>> = 13.758394749894615

* indianrupee.inline: L<<129.0,272.0>--<176.0,274.0>>/L<<176.0,274.0>--<129.0,274.0>> = 2.436648246810141

* indianrupee.inline: L<<340.0,272.0>--<129.0,272.0>>/L<<129.0,272.0>--<176.0,274.0>> = 2.436648246810141

* onethird.inline: B<<997.5,291.0>-<990.0,271.0>-<957.0,264.0>>/L<<957.0,264.0>--<968.0,264.0>> = 11.976132444203333

* three.inline: B<<402.0,388.5>-<388.0,374.0>-<358.0,367.0>>/L<<358.0,367.0>--<374.0,367.0>> = 13.134022306396327

* three.sinf.inline: B<<312.5,291.0>-<305.0,271.0>-<272.0,264.0>>/L<<272.0,264.0>--<283.0,264.0>> = 11.976132444203333

* 7 more.

Use -F or --full-lists to disable shortening of long lists.

[code: found-jaggy-segments]

⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines?

• ⚠️ WARN

  The following glyphs have semi-vertical/semi-horizontal lines:

* M.v (U+FF4D): L<<179.0,36.0>--<183.0,684.0>>

* M.v (U+FF4D): L<<819.0,684.0>--<823.0,36.0>>

* M.v.inline: L<<277.0,90.0>--<279.0,599.0>>

* M.v.inline: L<<289.0,599.0>--<287.0,90.0>>

* M.v.inline: L<<705.0,90.0>--<703.0,599.0>>

* M.v.inline: L<<713.0,599.0>--<715.0,90.0>>

* asciicircum (U+005E): L<<202.0,171.0>--<70.0,172.0>>

* asciicircum (U+005E): L<<609.0,172.0>--<477.0,171.0>>

* ascript (U+0251): L<<675.0,530.0>--<677.0,36.0>>

[code: found-semi-vertical]

⚠️ WARN Ensure dotted circle glyph is present and can attach marks.

• ⚠️ WARN

  No dotted circle glyph present

  
  [code: missing-dotted-circle]

⚠️ 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+02BE MODIFIER LETTER RIGHT HALF RING: not included in any glyphset definition
• U+02BF MODIFIER LETTER LEFT HALF RING: not included in any glyphset definition
• U+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh, yi
• U+02C8 MODIFIER LETTER VERTICAL LINE: not included in any glyphset definition
• U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
• U+02CA MODIFIER LETTER ACUTE ACCENT: not included in any glyphset definition
• U+02CB MODIFIER LETTER GRAVE ACCENT: not included in any glyphset definition
• U+02CC MODIFIER LETTER LOW VERTICAL LINE: not included in any glyphset definition
• U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
• U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi 535 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, vietnamese

[code: unreachable-subsetting]

⚠️ WARN Is there kerning info for non-ligated sequences?

• ⚠️ WARN

  GPOS table lacks kerning info for the following non-ligated sequences:

- I.salt_v + I.salt_v

[code: lacks-kern-info]

⚠️ WARN Are there caret positions declared for every ligature?

• ⚠️ WARN

  This font lacks caret position values for ligature glyphs on its GDEF table.

  
  [code: lacks-caret-pos]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.

• ⚠️ WARN

  This font file does not have a 'meta' table.

  
  [code: lacks-meta-table]

ℹ️ INFO List all superfamily filepaths

• ℹ️ INFO

  ofl/bungeetint

  
  [code: family-path]

ℹ️ INFO Font contains all required tables?

• ℹ️ INFO

  This font contains the following optional tables:

- loca

- prep

- GPOS

- GSUB

- gasp

- vhea

- vmtx

[code: optional-tables]

ℹ️ INFO EPAR table present in font?

• ℹ️ 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?

• ℹ️ 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 Show hinting filesize impact.

• ℹ️ INFO

  Hinting filesize impact:

	ofl/bungeetint/BungeeTint-Regular.ttf
Dehinted Size	216.6kb
Hinted Size	216.7kb
Increase	24 bytes
Change	0.0 %

[code: size-impact]

ℹ️ INFO Font has old ttfautohint applied?

• ℹ️ INFO

  Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 2.001']

  
  [code: version-not-detected]

[1] Family checks

ℹ️ INFO Check axis ordering on the STAT table.

• ℹ️ INFO

  All of the fonts lack a STAT table.

  
  [code: summary]

Summary

💥 ERROR	☠ FATAL	🔥 FAIL	⚠️ WARN	⏩ SKIP	ℹ️ INFO	✅ PASS	🔎 DEBUG
0	0	2	12	70	7	161	0
0%	0%	1%	5%	28%	3%	64%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[vv-monsalve]

• 🔥 FAIL Check accent of Lcaron, dcaron, lcaron, tcaron
  They are decomposed glyphs and the font is all caps.

• 🔥 FAIL Does DESCRIPTION file contain broken links?
  TN said they will fix the link

[emmamarichal]

Hi @vv-monsalve, I put here the "weird" thigns I saw. Some of them are probably to ignore, but I put them here just in case!

. . .

[github-actions]

FontBakery report

fontbakery version: 0.12.9

Check results

[20] BungeeTint-Regular.ttf

🔥 FAIL Check accent of Lcaron, dcaron, lcaron, tcaron

• 🔥 FAIL

  dcaron uses component caroncmb.

  
  [code: wrong-mark]

• 🔥 FAIL

  tcaron uses component caroncmb.

  
  [code: wrong-mark]

• ⚠️ WARN

  Lcaron is decomposed and therefore could not be checked. Please check manually.

  
  [code: decomposed-outline]

• ⚠️ WARN

  lcaron is composed of a single component and therefore could not be checked. Please check manually.

  
  [code: single-component]

🔥 FAIL Does DESCRIPTION file contain broken links?

• 🔥 FAIL

  The following links are broken in the article file:
  https://fontbureau.com (status code: 404)

  
  [code: broken-links]

⚠️ WARN Check glyphs in mark glyph class are non-spacing.

• ⚠️ WARN

  The following spacing glyphs may be in the GDEF mark glyph class by mistake:
  commaaccent (U+0326), commaaccent (U+F6C3) and commaaccent.inline (unencoded)

  
  [code: spacing-mark-glyphs]

⚠️ WARN Check mark characters are in GDEF mark glyph class.

• ⚠️ WARN

  The following mark characters could be in the GDEF mark glyph class:
  horncmb (U+031B)

  
  [code: mark-chars]

⚠️ WARN Check if each glyph has the recommended amount of contours.

• ⚠️ 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: aring	Contours detected: 3	Expected: 4


Glyph name: ae	Contours detected: 2	Expected: 3


Glyph name: egrave	Contours detected: 2	Expected: 3


Glyph name: eacute	Contours detected: 2	Expected: 3


65 more.

Use -F or --full-lists to disable shortening of long lists.

[code: contour-count]

⚠️ WARN Check math signs have the same width.

• ⚠️ WARN

  The most common width is 734 among a set of 9 math glyphs.
  The following math glyphs have a different width, though:

Width = 714: greater, less, greaterequal, lessequal

[code: width-outliers]

⚠️ 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:
  blackdownpointingtriangle.inline, blackleftpointingtriangle.inline, blackrightpointingtriangle.inline, indexdownleft.salt_outline.inline, indexdownright.salt_outline.inline, indexupright.salt_outline.inline, whitedownpointingtriangle.inline, whiteleftpointingtriangle.inline and whiterightpointingtriangle.inline

  
  [code: legacy-long-names]

⚠️ WARN Do outlines contain any jaggy segments?

• ⚠️ WARN

  The following glyphs have jaggy segments:

* indexdownleft.outline (U+E142): L<<538.0,163.0>--<475.0,110.0>>/L<<475.0,110.0>--<477.0,111.0>> = 13.50783887527299

* indexdownright.outline (U+E143): L<<523.0,111.0>--<525.0,110.0>>/L<<525.0,110.0>--<462.0,163.0>> = 13.50783887527299

* indexupleft.outline (U+E144): L<<303.0,322.0>--<250.0,385.0>>/L<<250.0,385.0>--<251.0,383.0>> = 13.50783887527299

* indexupright.outline (U+E145): L<<749.0,383.0>--<750.0,385.0>>/L<<750.0,385.0>--<697.0,322.0>> = 13.50783887527299

* indianrupee.inline: B<<366.5,320.5>-<354.0,291.0>-<316.0,280.0>>/L<<316.0,280.0>--<340.0,281.0>> = 13.758394749894615

* indianrupee.inline: L<<129.0,272.0>--<176.0,274.0>>/L<<176.0,274.0>--<129.0,274.0>> = 2.436648246810141

* indianrupee.inline: L<<340.0,272.0>--<129.0,272.0>>/L<<129.0,272.0>--<176.0,274.0>> = 2.436648246810141

* onethird.inline: B<<997.5,291.0>-<990.0,271.0>-<957.0,264.0>>/L<<957.0,264.0>--<968.0,264.0>> = 11.976132444203333

* three.inline: B<<402.0,388.5>-<388.0,374.0>-<358.0,367.0>>/L<<358.0,367.0>--<374.0,367.0>> = 13.134022306396327

* three.sinf.inline: B<<312.5,291.0>-<305.0,271.0>-<272.0,264.0>>/L<<272.0,264.0>--<283.0,264.0>> = 11.976132444203333

* 7 more.

Use -F or --full-lists to disable shortening of long lists.

[code: found-jaggy-segments]

⚠️ WARN Do outlines contain any semi-vertical or semi-horizontal lines?

• ⚠️ WARN

  The following glyphs have semi-vertical/semi-horizontal lines:

* M.v (U+FF4D): L<<179.0,36.0>--<183.0,684.0>>

* M.v (U+FF4D): L<<819.0,684.0>--<823.0,36.0>>

* M.v.inline: L<<277.0,90.0>--<279.0,599.0>>

* M.v.inline: L<<289.0,599.0>--<287.0,90.0>>

* M.v.inline: L<<705.0,90.0>--<703.0,599.0>>

* M.v.inline: L<<713.0,599.0>--<715.0,90.0>>

* asciicircum (U+005E): L<<202.0,171.0>--<70.0,172.0>>

* asciicircum (U+005E): L<<609.0,172.0>--<477.0,171.0>>

* ascript (U+0251): L<<675.0,530.0>--<677.0,36.0>>

[code: found-semi-vertical]

⚠️ WARN Ensure dotted circle glyph is present and can attach marks.

• ⚠️ WARN

  No dotted circle glyph present

  
  [code: missing-dotted-circle]

⚠️ 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+02BE MODIFIER LETTER RIGHT HALF RING: not included in any glyphset definition
• U+02BF MODIFIER LETTER LEFT HALF RING: not included in any glyphset definition
• U+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh, yi
• U+02C8 MODIFIER LETTER VERTICAL LINE: not included in any glyphset definition
• U+02C9 MODIFIER LETTER MACRON: not included in any glyphset definition
• U+02CA MODIFIER LETTER ACUTE ACCENT: not included in any glyphset definition
• U+02CB MODIFIER LETTER GRAVE ACCENT: not included in any glyphset definition
• U+02CC MODIFIER LETTER LOW VERTICAL LINE: not included in any glyphset definition
• U+02D8 BREVE: try adding one of: canadian-aboriginal, yi
• U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi 535 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, vietnamese

[code: unreachable-subsetting]

⚠️ WARN Is there kerning info for non-ligated sequences?

• ⚠️ WARN

  GPOS table lacks kerning info for the following non-ligated sequences:

- I.salt_v + I.salt_v

[code: lacks-kern-info]

⚠️ WARN Are there caret positions declared for every ligature?

• ⚠️ WARN

  This font lacks caret position values for ligature glyphs on its GDEF table.

  
  [code: lacks-caret-pos]

⚠️ WARN Ensure fonts have ScriptLangTags declared on the 'meta' table.

• ⚠️ WARN

  This font file does not have a 'meta' table.

  
  [code: lacks-meta-table]

ℹ️ INFO List all superfamily filepaths

• ℹ️ INFO

  ofl/bungeetint

  
  [code: family-path]

ℹ️ INFO Font contains all required tables?

• ℹ️ INFO

  This font contains the following optional tables:

- loca

- prep

- GPOS

- GSUB

- gasp

- vhea

- vmtx

[code: optional-tables]

ℹ️ INFO EPAR table present in font?

• ℹ️ 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?

• ℹ️ 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 Show hinting filesize impact.

• ℹ️ INFO

  Hinting filesize impact:

	ofl/bungeetint/BungeeTint-Regular.ttf
Dehinted Size	216.6kb
Hinted Size	216.7kb
Increase	24 bytes
Change	0.0 %

[code: size-impact]

ℹ️ INFO Font has old ttfautohint applied?

• ℹ️ INFO

  Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 2.001']

  
  [code: version-not-detected]

[1] Family checks

ℹ️ INFO Check axis ordering on the STAT table.

• ℹ️ INFO

  All of the fonts lack a STAT table.

  
  [code: summary]

Summary

💥 ERROR	☠ FATAL	🔥 FAIL	⚠️ WARN	⏩ SKIP	ℹ️ INFO	✅ PASS	🔎 DEBUG
0	0	2	12	70	7	161	0
0%	0%	1%	5%	28%	3%	64%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG