Red Hat Mono: Version 1.010 added

[RosaWagner]

f9e0fb5: [gftools-packager] Red Hat Mono: Version 1.010 added

• Red Hat Mono Version 1.010 taken from the upstream repo https://github.com/jeremymickel/RedHatFonts at commit jeremymickel/RedHatFonts@9dd2dd5.

7187819: [gftools-packager] ofl/redhatmono remove METADATA "source". #2587

[RosaWagner]

Updated

Red Hat Mono: Version 1.010 added

---

6ec2f30: [gftools-packager] Red Hat Mono: Version 1.010 added

• Red Hat Mono Version 1.010 taken from the upstream repo https://github.com/jeremymickel/RedHatFonts at commit jeremymickel/RedHatFonts@9dd2dd5.

209eddf: [gftools-packager] ofl/redhatmono remove METADATA "source". #2587

[RosaWagner]

1. The instances in the fvar table are not in the right order, but after testing in several app, it doesn't mess up the dropdown menu. I do think that it should be fixed though, because we don't know how non-tested environments would react.

2. The missing SemiBold instance has been discussing with the designer during a meeting. He is against including it. I leave @davelab6 decides if he wants to merge it anyway given that this font was prioritised, or continuing the conversation with the designer to convince him otherwise.

[gf-bot]

Fontbakery report

Fontbakery version: 0.7.37

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

• com.google.fonts/check/ftxvalidator_is_available

--- Rationale ---
There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.
If Font Bakery is not running on an OSX machine, the machine running Font Bakery
could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure call
(rpc).
There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/main/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

• ⚠ WARN Could not find ftxvalidator. [code: ftxvalidator-available]

[7] RedHatMono-Italic[wght].ttf

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

• com.google.fonts/check/metadata/designer_profiles

• 🔥 FAIL Designer MCKL listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

• com.google.fonts/check/metadata/listed_on_gfonts

• ⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts

• com.google.fonts/check/repo/vf_has_static_fonts

--- Rationale ---
Variable font family directories kept in the google/fonts git repo may include a
static/ subdir containing static fonts.
These files are meant to be served for users that still lack support for
variable fonts in their web browsers.

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

⚠ WARN: Ensure Stylistic Sets have description.

• com.google.fonts/check/stylisticset_description

--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.

• ⚠ WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
• ⚠ WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

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

• 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:
  acute, breve, caron, cedilla, circumflex, commaaccent, dieresis, dotaccent, grave, hungarumlaut and 4 more. [code: spacing-mark-glyphs]

⚠ WARN: Check GDEF mark glyph class doesn't have characters that are not marks)

• com.google.fonts/check/gdef_non_mark_chars

--- Rationale ---
Glyphs in the GDEF mark glyph class become non-spacing and may be repositioned
if they have mark anchors.
Only combining mark glyphs should be in that class. Any non-mark glyph must not
be in that class, in particular spacing glyphs.

• ⚠ WARN The following non-mark characters should not be in the GDEF mark glyph class:
  U+0060, U+00A8, U+00AF, U+00B4, U+00B8, U+02C6, U+02C7, U+02D8, U+02D9, U+02DA, U+02DB, U+02DC and U+02DD [code: non-mark-chars]

⚠ WARN: Are there any misaligned on-curve points?

• [com.google.fonts/check/outline_alignment_miss](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.html#com.google.fonts/check/outline_alignment_miss)

--- Rationale ---
This check heuristically looks for on-curve points which are close to, but do
not sit on, significant boundary coordinates. For example, a point which has a
Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the
baseline, here we also check for points near the x-height (but only for lower
case Latin letters), cap-height, ascender and descender Y coordinates.
Not all such misaligned curve points are a mistake, and sometimes the design may
call for points in locations near the boundaries. As this check is liable to
generate significant numbers of false positives, it will pass if there are more
than 100 reported misalignments.

• ⚠ WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:
  • Uogonek: X=353.0,Y=-1.0 (should be at baseline 0?)
  • i: X=351.0,Y=702.0 (should be at cap-height 700?)
  • j: X=444.5,Y=702.0 (should be at cap-height 700?)
  • abreve: X=232.0,Y=698.0 (should be at cap-height 700?)
  • ae: X=456.0,Y=2.0 (should be at baseline 0?)
  • ccaron: X=238.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=279.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=465.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=511.0,Y=698.0 (should be at cap-height 700?)
  • ebreve: X=225.0,Y=698.0 (should be at cap-height 700?) and 52 more. [code: found-misalignments]

[7] RedHatMono[wght].ttf

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

• com.google.fonts/check/metadata/designer_profiles

• 🔥 FAIL Designer MCKL listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

• com.google.fonts/check/metadata/listed_on_gfonts

• ⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts

• com.google.fonts/check/repo/vf_has_static_fonts

--- Rationale ---
Variable font family directories kept in the google/fonts git repo may include a
static/ subdir containing static fonts.
These files are meant to be served for users that still lack support for
variable fonts in their web browsers.

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

⚠ WARN: Ensure Stylistic Sets have description.

• com.google.fonts/check/stylisticset_description

--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.

• ⚠ WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
• ⚠ WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

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

• 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:
  acute, breve, caron, cedilla, circumflex, commaaccent, dieresis, dotaccent, grave, hungarumlaut and 4 more. [code: spacing-mark-glyphs]

⚠ WARN: Check GDEF mark glyph class doesn't have characters that are not marks)

• com.google.fonts/check/gdef_non_mark_chars

--- Rationale ---
Glyphs in the GDEF mark glyph class become non-spacing and may be repositioned
if they have mark anchors.
Only combining mark glyphs should be in that class. Any non-mark glyph must not
be in that class, in particular spacing glyphs.

• ⚠ WARN The following non-mark characters should not be in the GDEF mark glyph class:
  U+0060, U+00A8, U+00AF, U+00B4, U+00B8, U+02C6, U+02C7, U+02D8, U+02D9, U+02DA, U+02DB, U+02DC and U+02DD [code: non-mark-chars]

⚠ WARN: Are there any misaligned on-curve points?

• [com.google.fonts/check/outline_alignment_miss](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.html#com.google.fonts/check/outline_alignment_miss)

--- Rationale ---
This check heuristically looks for on-curve points which are close to, but do
not sit on, significant boundary coordinates. For example, a point which has a
Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the
baseline, here we also check for points near the x-height (but only for lower
case Latin letters), cap-height, ascender and descender Y coordinates.
Not all such misaligned curve points are a mistake, and sometimes the design may
call for points in locations near the boundaries. As this check is liable to
generate significant numbers of false positives, it will pass if there are more
than 100 reported misalignments.

• ⚠ WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:
  • IJ: X=263.5,Y=-0.5 (should be at baseline 0?)
  • Oslash: X=520.0,Y=701.0 (should be at cap-height 700?)
  • Oslash: X=576.0,Y=701.0 (should be at cap-height 700?)
  • ccaron: X=162.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=206.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=396.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=440.0,Y=698.0 (should be at cap-height 700?)
  • ecaron: X=159.0,Y=698.0 (should be at cap-height 700?)
  • ecaron: X=203.0,Y=698.0 (should be at cap-height 700?)
  • ecaron: X=393.0,Y=698.0 (should be at cap-height 700?) and 30 more. [code: found-misalignments]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	2	13	100	17	261	0
0%	1%	3%	25%	4%	66%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• INFO
• PASS
• DEBUG

[davelab6]

Should be Copyright 2021 The Red Hat Project Authors (https://github.com/RedHatOfficial/RedHatFont)

I'm curious how this other notice made its way in here :)

[RosaWagner]

I linked the OFL directly with packager, it is the actual file upstream. How could I miss it ?!

[RosaWagner]

I made a PR upstream

[gf-bot]

Fontbakery report

Fontbakery version: 0.7.37

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

• com.google.fonts/check/ftxvalidator_is_available

--- Rationale ---
There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.
If Font Bakery is not running on an OSX machine, the machine running Font Bakery
could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure call
(rpc).
There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/main/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

• ⚠ WARN Could not find ftxvalidator. [code: ftxvalidator-available]

[8] RedHatMono-Italic[wght].ttf

🔥 FAIL: DESCRIPTION.en_us.html must have less than 1000 bytes.

• com.google.fonts/check/description/max_length

• 🔥 FAIL DESCRIPTION.en_us.html must have size smaller than 1000 bytes. [code: too-long]

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

• com.google.fonts/check/metadata/designer_profiles

• 🔥 FAIL Designer MCKL listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

• com.google.fonts/check/metadata/listed_on_gfonts

• ⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts

• com.google.fonts/check/repo/vf_has_static_fonts

--- Rationale ---
Variable font family directories kept in the google/fonts git repo may include a
static/ subdir containing static fonts.
These files are meant to be served for users that still lack support for
variable fonts in their web browsers.

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

⚠ WARN: Ensure Stylistic Sets have description.

• com.google.fonts/check/stylisticset_description

--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.

• ⚠ WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
• ⚠ WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

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

• 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:
  acute, breve, caron, cedilla, circumflex, commaaccent, dieresis, dotaccent, grave, hungarumlaut and 4 more. [code: spacing-mark-glyphs]

⚠ WARN: Check GDEF mark glyph class doesn't have characters that are not marks)

• com.google.fonts/check/gdef_non_mark_chars

--- Rationale ---
Glyphs in the GDEF mark glyph class become non-spacing and may be repositioned
if they have mark anchors.
Only combining mark glyphs should be in that class. Any non-mark glyph must not
be in that class, in particular spacing glyphs.

• ⚠ WARN The following non-mark characters should not be in the GDEF mark glyph class:
  U+0060, U+00A8, U+00AF, U+00B4, U+00B8, U+02C6, U+02C7, U+02D8, U+02D9, U+02DA, U+02DB, U+02DC and U+02DD [code: non-mark-chars]

⚠ WARN: Are there any misaligned on-curve points?

• [com.google.fonts/check/outline_alignment_miss](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.html#com.google.fonts/check/outline_alignment_miss)

--- Rationale ---
This check heuristically looks for on-curve points which are close to, but do
not sit on, significant boundary coordinates. For example, a point which has a
Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the
baseline, here we also check for points near the x-height (but only for lower
case Latin letters), cap-height, ascender and descender Y coordinates.
Not all such misaligned curve points are a mistake, and sometimes the design may
call for points in locations near the boundaries. As this check is liable to
generate significant numbers of false positives, it will pass if there are more
than 100 reported misalignments.

• ⚠ WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:
  • Uogonek: X=353.0,Y=-1.0 (should be at baseline 0?)
  • i: X=351.0,Y=702.0 (should be at cap-height 700?)
  • j: X=444.5,Y=702.0 (should be at cap-height 700?)
  • abreve: X=232.0,Y=698.0 (should be at cap-height 700?)
  • ae: X=456.0,Y=2.0 (should be at baseline 0?)
  • ccaron: X=238.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=279.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=465.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=511.0,Y=698.0 (should be at cap-height 700?)
  • ebreve: X=225.0,Y=698.0 (should be at cap-height 700?) and 52 more. [code: found-misalignments]

[8] RedHatMono[wght].ttf

🔥 FAIL: DESCRIPTION.en_us.html must have less than 1000 bytes.

• com.google.fonts/check/description/max_length

• 🔥 FAIL DESCRIPTION.en_us.html must have size smaller than 1000 bytes. [code: too-long]

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

• com.google.fonts/check/metadata/designer_profiles

• 🔥 FAIL Designer MCKL listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?

• com.google.fonts/check/metadata/listed_on_gfonts

• ⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts

• com.google.fonts/check/repo/vf_has_static_fonts

--- Rationale ---
Variable font family directories kept in the google/fonts git repo may include a
static/ subdir containing static fonts.
These files are meant to be served for users that still lack support for
variable fonts in their web browsers.

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

⚠ WARN: Ensure Stylistic Sets have description.

• com.google.fonts/check/stylisticset_description

--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.

• ⚠ WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
• ⚠ WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

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

• 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:
  acute, breve, caron, cedilla, circumflex, commaaccent, dieresis, dotaccent, grave, hungarumlaut and 4 more. [code: spacing-mark-glyphs]

⚠ WARN: Check GDEF mark glyph class doesn't have characters that are not marks)

• com.google.fonts/check/gdef_non_mark_chars

--- Rationale ---
Glyphs in the GDEF mark glyph class become non-spacing and may be repositioned
if they have mark anchors.
Only combining mark glyphs should be in that class. Any non-mark glyph must not
be in that class, in particular spacing glyphs.

• ⚠ WARN The following non-mark characters should not be in the GDEF mark glyph class:
  U+0060, U+00A8, U+00AF, U+00B4, U+00B8, U+02C6, U+02C7, U+02D8, U+02D9, U+02DA, U+02DB, U+02DC and U+02DD [code: non-mark-chars]

⚠ WARN: Are there any misaligned on-curve points?

• [com.google.fonts/check/outline_alignment_miss](https://font-bakery.readthedocs.io/en/latest/fontbakery/profiles/<Section: Outline Correctness Checks>.html#com.google.fonts/check/outline_alignment_miss)

--- Rationale ---
This check heuristically looks for on-curve points which are close to, but do
not sit on, significant boundary coordinates. For example, a point which has a
Y-coordinate of 1 or -1 might be a misplaced baseline point. As well as the
baseline, here we also check for points near the x-height (but only for lower
case Latin letters), cap-height, ascender and descender Y coordinates.
Not all such misaligned curve points are a mistake, and sometimes the design may
call for points in locations near the boundaries. As this check is liable to
generate significant numbers of false positives, it will pass if there are more
than 100 reported misalignments.

• ⚠ WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:
  • IJ: X=263.5,Y=-0.5 (should be at baseline 0?)
  • Oslash: X=520.0,Y=701.0 (should be at cap-height 700?)
  • Oslash: X=576.0,Y=701.0 (should be at cap-height 700?)
  • ccaron: X=162.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=206.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=396.0,Y=698.0 (should be at cap-height 700?)
  • ccaron: X=440.0,Y=698.0 (should be at cap-height 700?)
  • ecaron: X=159.0,Y=698.0 (should be at cap-height 700?)
  • ecaron: X=203.0,Y=698.0 (should be at cap-height 700?)
  • ecaron: X=393.0,Y=698.0 (should be at cap-height 700?) and 30 more. [code: found-misalignments]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	4	13	100	17	259	0
0%	1%	3%	25%	4%	66%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• INFO
• PASS
• DEBUG

[m4rc1e]

LGTM. Thanks