4 scripts merged into 1 font

RosaWagner commented 4 years ago

The font is almost ready for Google :)

[ ] Can you make sure the indic script are working properly ? Fontbakery is raising warning about the mark glyph class, so maybe some should have anchors et reciprocally.
[ ] Glyphs has changed its glyph-naming scheme and its charset, you maybe want to check missing glyphs and renamed glyphs. (see commit description)

Fontbakery report --variable

Fontbakery version: 0.7.27

[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.

[4] Arima[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 'NDIS' 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: 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	4	75	7	88	0
0%	1%	2%	43%	4%	50%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

Fontbakery report --static

Fontbakery version: 0.7.27

[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.

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

[5] Arima-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** OS/2 VendorID value 'NDIS' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]

⚠ WARN: Check 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: uni200C Contours detected: 1 Expected: 0 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: filledbox Contours detected: 4 Expected: 1 Glyph name: uni25C6 Contours detected: 4 Expected: 1 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: lozenge Contours detected: 4 Expected: 2 Glyph name: asterisk Contours detected: 7 Expected: 1 or 4 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: uni200C Contours detected: 1 Expected: 0 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: fi Contours detected: 2 Expected: 3 Glyph name: Sigma Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: uni200D Contours detected: 1 Expected: 0 Glyph name: uni25C6 Contours detected: 4 Expected: 1 [code: contour-count]

⚠ 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 [code: lacks-kern-info]

⚠ WARN: Check mark characters are in GDEF mark glyph class)

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

--- Rationale ---

Glyphs in the GDEF mark glyph class should be non-spacing.
Spacing glyphs in the GDEF mark glyph class may have incorrect anchor
positioning that was only intended for building composite glyphs during design.

* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uMatra_halantmalayalam, uni0D02, uni0D03, uni0D3E, uni0D3F, uni0D40, uni0D41, uni0D42, uni0D43, uni0D44 and 8 more. [code: spacing-mark-glyphs]

⚠ WARN: Check mark characters are in GDEF mark glyph class

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

--- Rationale ---

Mark characters should be in the GDEF mark glyph class.

* ⚠ **WARN** The following mark characters could be in the GDEF mark glyph class: U+0BBE, U+0BBF, U+0BC1, U+0BC2, U+0BC6, U+0BC7, U+0BC8, U+0BCA, U+0BCB, U+0BCC and U+0BD7 [code: mark-chars]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	35	533	42	530	0
0%	0%	3%	47%	4%	46%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

NDISCOVER commented 2 years ago

Hi! I wanted to merge but is "closed". is this normal?

RosaWagner commented 2 years ago

Yeah this is the old one, using old sources, I gonna PR updated version of Naxos only, and Yanone will do the merge

NDISCOVER / Arima-Font