#2 GF Update: small-fixes

Font v.2.000 is ready to be updated on Google Fonts — "design" related issues for the next release (v-3.000).

Some of our fonts respecting our last spec (improving output for fvar and stat tables) revealed a bug with the sliders in Indesign. We decided to keep the fonts this way — since the bug comes more likely from Indesign. We are waiting for updates from Adobe to better support variable fonts.
Normally, remaining checks can be ignored (even the name length, since the number of characters is still inferior to 29 signs)

Fontbakery report — Variable

Fontbakery version: 0.7.29

[1] Family checks

🔥 FAIL: Do we have the latest version of FontBakery installed?

* [com.google.fonts/check/fontbakery_version](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/universal.html#com.google.fonts/check/fontbakery_version) * 🔥 **FAIL** Unable to detect what's the latest version of FontBakery available. Maybe we're offline? Please check Internet access and try again.

[3] PublicSans-Italic[wght].ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

* ⚠ **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: Are there caret positions declared for every ligature?

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

* ⚠ **WARN** This font lacks caret positioning values for these ligature glyphs: - colon_f_l_a_g_colon.liga - colon_f_l_a_g_two_colon.liga - colon_one_eight_F_colon.liga [code: incomplete-caret-pos-data]

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

* [com.google.fonts/check/kerning_for_non_ligated_sequences](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/kerning_for_non_ligated_sequences)

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

* ⚠ **WARN** GPOS table lacks kerning info for the following non-ligated sequences: - f + i - i + l - colon + f - f + l - l + a - a + g - g + two - two + colon - g + colon - colon + one - one + eight - eight + F - F + colon [code: lacks-kern-info]

[3] PublicSans[wght].ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	6	158	14	161	0
0%	0%	2%	46%	4%	47%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

Fontbakery report — Statics

Fontbakery version: 0.7.29

[1] Family checks

🔥 FAIL: Do we have the latest version of FontBakery installed?

[5] PublicSans-Black.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 5 Expected: 1, 3, 4 or 7 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni20A9 Contours detected: 5 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

* ⚠ **WARN** This font lacks caret positioning values for these ligature glyphs: - colon_one_eight_F_colon.liga - colon_f_l_a_g_colon.liga - colon_f_l_a_g_two_colon.liga [code: incomplete-caret-pos-data]

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-BlackItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 5 Expected: 1, 3, 4 or 7 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: uni20A9 Contours detected: 5 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-Bold.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-BoldItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[6] PublicSans-ExtraBold.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

⚠ WARN: Combined length of family and style must not exceed 27 characters.

* [com.google.fonts/check/name/family_and_style_max_length](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/name/family_and_style_max_length)

--- Rationale ---

According to a GlyphsApp tutorial [1], in order to make sure all versions of
Windows recognize it as a valid font file, we must make sure that the
concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style
(NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20
characters.

After discussing the problem in more detail at `FontBakery issue #2179 [2] we
decided that allowing up to 27 chars would still be on the safe side, though.

[1]
https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances
[2] https://github.com/googlefonts/fontbakery/issues/2179

* ⚠ **WARN** The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries: FONT_FAMILY_NAME = 'Public Sans ExtraBold' / SUBFAMILY_NAME = 'Regular' Please take a look at the conversation at https://github.com/googlefonts/fontbakery/issues/2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

[5] PublicSans-ExtraBoldItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 5 Expected: 1, 3, 4 or 7 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: uni20A9 Contours detected: 5 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[6] PublicSans-ExtraLight.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

⚠ WARN: Combined length of family and style must not exceed 27 characters.

* [com.google.fonts/check/name/family_and_style_max_length](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/name/family_and_style_max_length)

--- Rationale ---

According to a GlyphsApp tutorial [1], in order to make sure all versions of
Windows recognize it as a valid font file, we must make sure that the
concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style
(NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20
characters.

After discussing the problem in more detail at `FontBakery issue #2179 [2] we
decided that allowing up to 27 chars would still be on the safe side, though.

[1]
https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances
[2] https://github.com/googlefonts/fontbakery/issues/2179

* ⚠ **WARN** The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries: FONT_FAMILY_NAME = 'Public Sans ExtraLight' / SUBFAMILY_NAME = 'Regular' Please take a look at the conversation at https://github.com/googlefonts/fontbakery/issues/2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

[6] PublicSans-ExtraLightItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

⚠ WARN: Combined length of family and style must not exceed 27 characters.

* [com.google.fonts/check/name/family_and_style_max_length](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/name/family_and_style_max_length)

--- Rationale ---

According to a GlyphsApp tutorial [1], in order to make sure all versions of
Windows recognize it as a valid font file, we must make sure that the
concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style
(NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20
characters.

After discussing the problem in more detail at `FontBakery issue #2179 [2] we
decided that allowing up to 27 chars would still be on the safe side, though.

[1]
https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances
[2] https://github.com/googlefonts/fontbakery/issues/2179

* ⚠ **WARN** The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries: FONT_FAMILY_NAME = 'Public Sans ExtraLight' / SUBFAMILY_NAME = 'Italic' Please take a look at the conversation at https://github.com/googlefonts/fontbakery/issues/2179 in order to understand the reasoning behind these name table records max-length criteria. [code: too-long]

[5] PublicSans-Italic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

* [com.google.fonts/check/production_glyphs_similarity](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/production_glyphs_similarity) * ⚠ **WARN** Following glyphs differ greatly from Google Fonts version: [five, acircumflex, uni1EA3, lozenge, onehalf, uni1EB6, nine.subs, Eth, Racute, Oacute, uni1ED7, dagger, uni1ECC, eight, uni0326, i.loclTRK, comma.tf, jcircumflex, Ohorn, franc.tf, uogonek, Eacute, period, oacute, uni1E6C, uni0304, quotedblbase, aring, franc, uni2219, uni1ECE, wcircumflex, breve, uni01EA, emptyset, fl, uni1EDF, d, egrave, uni0201, Scaron, wacute, Udieresis, uacute, oslash, lira, one.dnom, uni0307, zero.dnom, uni030C, Rcaron, three.osf, eight.osf, semicolon, Itilde, Uhungarumlaut, Aacute, uni1EAE, uni0216, uni0214, p, threequarters, quotedblright, uni1ECF, uni1EF7, ugrave, three.numr, ampersand, Iogonek, six.subs, uni1E63, florin, dieresis, iacute, five.tf, periodcentered, slash, uni03060309, Scedilla, Ydieresis, g, uni1EAA, uni1EB2, uni1EF4, uni2153, uni1ED3, O, uni0162, D, approxequal, uni030C.alt, uni1E5A, uni01D4, uni2117, uni1EA4, Ucircumflex, uni1EE1, K, hyphen, uni0210, Tbar, uni1E24, exclamdown, uni1EE0, uni020D, uni20A9, AE, udieresis, uni1EDA, uni1EC3, uni1EF0, ldot, quotedbl, yen.tf, ydieresis, uni0215, uni1E93, uni1ECB, five.subs, Thorn, lslash, six.tf, uni2077, summation, greaterequal, Ygrave, uni1EF9, uni1EB5, two.dnom, currency, zero, caron, uni1EEE, Yacute, Zcaron, ibreve, Omacron, uni02BC, uni1EB8, eacute, uni0123, eth, Gbreve, copyright, Wdieresis, gcircumflex, uni2154, Lslash, uni1EC7, Idieresis, ccaron, b, uni1EE3, umacron, otilde, ccedilla, Egrave, Gcircumflex, Ncaron, uni03060300, dollar, s, three.tf, uni02BB, ntilde, wgrave, bullet, greater, ohungarumlaut, Umacron, seven.numr, l, five.osf, uni1EED, uni03060303, dollar.tf, odieresis, uni0302, adieresis, parenright, uni030A, dotlessi, nine.tf, sacute, zcaron, seven.subs, Emacron, seven, F, guilsinglleft, Ntilde, uni020C, lacute, uni1ED5, uni1EC6, lessequal, Uring, uni1EDD, Ibreve, aringacute, ohorn, oslashacute, five.dnom, zdotaccent, E, L, less, uni013B, uni1EA2, uni1ED8, uring, uni00B9, emdash.alt, Uhorn, uni1EE4, three, colon, uni0206, Otilde, uni1EEF, uni1EC5, Igrave, acutecomb.viet, four.numr, yen, uni0200, six, sterling, multiply, R, uni0212, uni1ED2, notequal, X, uni0306, Ograve, Lacute, C, uni0157, uni0213, t, quotesingle, omacron, two.tf, one.osf, Edieresis, Z, Q, uni20BA.tf, itilde, ordmasculine, uni1EA5, Aring, uni0311, braceleft, uni1EE2, uni0208, colon_f_l_a_g_two_colon.liga, uni2113, macron, sterling.tf, circumflex, onequarter, Aogonek, nine, uni0217, uni0219, Oslashacute, Hcircumflex, uni1E0D, B, aacute, uni1EB3, fraction, uni0163, dcroat, o, zacute, eight.numr, N, Ldot, ecaron, w, paragraph, uni2075, uni1EBF, fi, uni1EA0, racute, uni0211, underscore, Adieresis, seven.osf, eogonek, Edotaccent, scaron, parenleft, Amacron, Ecaron, uni1ECD, five.numr, uni1EE7, ncaron, aogonek, quoteright, edieresis, uni030B, trademark, eight.dnom, uni0122, Obreve, uni2078, uni0145, guillemotright, uni1EA7, uni1EC8, uhungarumlaut, plusminus, uni0204, uni1EEB, G, z, dotbelowcomb, Hbar, uni1ECA, radical, one.tf, Atilde, asterisk, dong, uni20BA, ae, acute, four, Euro.tf, gbreve, Ccircumflex, uni1EC1, uni021A, i, uni1ED0, six.dnom, .notdef, cedilla, uni018F, uni1EE6, c, uni0308, hbar, uni2120, uni1EBE, amacron, logicalnot, tildecomb, gravecomb.viet, Ecircumflex, H, uni2070, ecircumflex, Nacute, pi, ucircumflex, imacron, percent, thorn, plus, uni0328, idieresis, dong.tf, uni0327, uni0237, x, edotaccent, partialdiff, zero.subs, l.ss01, cent.tf, iogonek, uni0136, abreve, uni1EBC, uni2116, uni2126, questiondown, uni1EE8, uni0209, P, uni0259, Dcroat, uni1EBA, comma, bracketleft, Acircumflex, two.subs, ogonek, T, six.osf, k, Lcaron, uni1EA9, seveneighths, AEacute, Jcircumflex, Euro, ygrave, uni020A, uni1EDB, hcircumflex, four.dnom, Utilde, y, minus, question, uni0203, backslash, uni03060301, cacute, four.osf, f, hungarumlaut, uni1EC2, ocircumflex, OE, Wacute, lcaron, uni1EC9, integral, uni1E6D, uni021B, atilde, colonmonetary.tf, Uogonek, three.dnom, uhorn, ubreve, Ccaron, Iacute, aeacute, q, tcaron, tilde, germandbls, two, m, Idotaccent, n, uni1EC0, uni1EB7, uni1EAF, Zdotaccent, bracketright, Wcircumflex, threeeighths, oe, Odieresis, uni00B5, uni1E62, guilsinglright, section, uni1EA6, Gdotaccent, e, M, uni1E25, cdotaccent, eight.tf, nine.numr, uni1EEA, fiveeighths, ebreve, A, Imacron, Sacute, W, uni20A6, exclam, zero.osf, seven.dnom, uni03020303, Ugrave, uni1EF1, eight.subs, Aringacute, uni1EA1, uni1EC4, uni1EDE, tbar, uni1EE5, ccircumflex, endash, bar, zero.tf, uni013C, uni0156, gdotaccent, lira.tf, four.subs, uni1EEC, utilde, Cdotaccent, u, Y, four.tf, uni2206, rcaron, Dcaron, grave, infinity, brokenbar, uni1EB0, nine.dnom, two.numr, wdieresis, two.osf, three.subs, agrave, quotesinglbase, quotedblleft, uni1E44, Zacute, Ubreve, uni1ED1, S, uni20B9, r, perthousand, uni1ED9, uni1EB1, uni1EBD, uni1EF8, uni01EB, oneeighth, ring, uni03020301, asciicircum, g.ss01, uni1E5B, gravecomb, uni1E45, uni03020309, dotaccent, Ohungarumlaut, fraction.alt, uni0205, one.numr, equal, hookabovecomb, uni020F, braceright, h, six.numr, uni20B9.tf, obreve, U, uni020B, a, I, cent, uni0146, uni1EDC, uni0218, Oslash, uni1EF6, uni1E0C, uni0207, uni03020300, acutecomb, Abreve, uni1EB4, Wgrave, uni00AD, uni030F, at, colon_f_l_a_g_colon.liga, ordfeminine, scedilla, florin.tf, emdash, Agrave, uni0137, one, Icircumflex, v, Eng, uni00B2, kgreenlandic, daggerdbl, uni1EAC, uni1ED4, Ycircumflex, uni1ED6, igrave, uni1EAB, uni2074, j, one.subs, registered, Tcaron, ycircumflex, Cacute, uni1EAD, nacute, uni0202, uni1EB9, scircumflex, colonmonetary, J, guillemotleft, ellipsis, zero.numr, Ebreve, Ocircumflex, uni00B3, uni2076, V, Scircumflex, product, eng, yacute, uni031B, uni2079, period.tf, degree, uni020E, nine.osf, uni1EBB, divide, numbersign, emacron, uni1EA8, dcaron, icircumflex, Uacute, asciitilde, seven.tf, uni1E92, Eogonek, ograve, quoteleft, uni1EF5, Ccedilla, uni1EE9]

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-Light.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-LightItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-Medium.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-MediumItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-Regular.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-SemiBold.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-SemiBoldItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-Thin.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

[5] PublicSans-ThinItalic.ttf

⚠ WARN: Checking OS/2 achVendID.

* [com.google.fonts/check/vendor_id](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/vendor_id)

--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.

⚠ WARN: Glyphs are similiar to Google Fonts version?

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

* [com.google.fonts/check/contour_count](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/contour_count)

--- Rationale ---

Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will
only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.

* ⚠ **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: aring Contours detected: 3 Expected: 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: oe Contours detected: 4 Expected: 3 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni01EA Contours detected: 3 Expected: 2 Glyph name: uni01EB Contours detected: 3 Expected: 2 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: aring Contours detected: 3 Expected: 4 Glyph name: aringacute Contours detected: 3 Expected: 4 or 5 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: OE Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: oe Contours detected: 4 Expected: 3 [code: contour-count]

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

* [com.google.fonts/check/ligature_carets](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/googlefonts.html#com.google.fonts/check/ligature_carets)

--- Rationale ---

All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.

If using GlyphsApp, ligature carets can be set directly on canvas by accessing
the `Glyph -> Set Anchors` menu option or by pressing the `Cmd+U` keyboard
shortcut.

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

--- Rationale ---

Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	93	1423	108	1323	0
0%	0%	3%	48%	4%	45%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

uswds / public-sans