Giter Site home page Giter Site logo

bellota-font's People

Contributors

kemie avatar yanone avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar

Forkers

davelab6 9hexa6

bellota-font's Issues

Outline misbehaviour

Hi, I had a quick look and found the following problem which I would like to ask you to address before I proceed:

The a has a corner issue in the Bold Italic, see screenshot: Bildschirmfoto 2019-10-25 um 14 51 01

Heavy Weight

I really like this font! But I was wondering if it would be possible to have a heavier weight?

Google Fonts QA report

Fontbakery report

Fontbakery version: 0.7.8

[4] Family checks
🔥 FAIL: Fonts have equal numbers of glyphs?
  • com.google.fonts/check/family/equal_numbers_of_glyphs
  • 🔥 FAIL BoldItalic has 904 glyphs while Bold has 910 glyphs. There are 6 different glyphs among them: dotaccentcombcomb, omicron, i.loclTRK, uni0338.case, two.alt, uni0312
  • 🔥 FAIL Italic has 904 glyphs while Bold has 910 glyphs. There are 6 different glyphs among them: dotaccentcombcomb, omicron, i.loclTRK, uni0338.case, two.alt, uni0312
  • 🔥 FAIL LightItalic has 904 glyphs while Bold has 910 glyphs. There are 6 different glyphs among them: dotaccentcombcomb, omicron, i.loclTRK, uni0338.case, two.alt, uni0312
🔥 FAIL: Fonts have equal glyph names?
  • com.google.fonts/check/family/equal_glyph_names
  • 🔥 FAIL Glyphname 'uni0338.case' is defined on Bold, Light, Regular but is missing on BoldItalic, Italic, LightItalic.
  • 🔥 FAIL Glyphname 'two.alt' is defined on Bold, Light, Regular but is missing on BoldItalic, Italic, LightItalic.
  • 🔥 FAIL Glyphname 'dotaccentcombcomb' is defined on Bold, Light, Regular but is missing on BoldItalic, Italic, LightItalic.
  • 🔥 FAIL Glyphname 'uni0312' is defined on Bold, Light, Regular but is missing on BoldItalic, Italic, LightItalic.
  • 🔥 FAIL Glyphname 'omicron' is defined on Bold, Light, Regular but is missing on BoldItalic, Italic, LightItalic.
  • 🔥 FAIL Glyphname 'i.loclTRK' is defined on Bold, Light, Regular but is missing on BoldItalic, Italic, LightItalic.
🔥 FAIL: Check that OS/2.fsSelection bold & italic settings are unique for each NameID1
🔥 FAIL: Verify that each group of fonts with the same nameID 1 has maximum of 4 fonts

[14] Bellota-Bold.ttf
🔥 FAIL: Checking OS/2 fsType.
  • com.google.fonts/check/fstype
  • 🔥 FAIL OS/2 fsType is a legacy DRM-related field.
    In this font it is set to 8 meaning that:
    The font may be embedded but must only be installed temporarily on other systems.
    No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
    Fonts with this setting indicate that they may be embedded and permanently installed on the remote system by an application.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Copyright notices match canonical pattern in fonts
🔥 FAIL: PPEM must be an integer on hinted fonts.
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
  • com.google.fonts/check/family/win_ascent_and_descent
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 1255, but got 1132 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 396, but got 329 instead [code: descent]
🔥 FAIL: Checking OS/2 Metrics match hhea Metrics.
🔥 FAIL: Whitespace and non-breaking space have the same width?
  • com.google.fonts/check/whitespace_widths
  • 🔥 FAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 312 font units wide, non-breaking space (uni00A0) is 350 font units wide. Both should be positive and the same.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ WARN Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
⚠ WARN: Check if each glyph has the recommended amount of contours.
  • com.google.fonts/check/contour_count
  • ⚠ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:

Glyph name: M Contours detected: 2 Expected: 1
Glyph name: f Contours detected: 2 Expected: 1
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: uni20A8 Contours detected: 1 Expected: 3
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: hcircumflex Contours detected: 1 Expected: 2
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcommaaccent Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni03D6 Contours detected: 1 Expected: 2
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2

⚠ WARN: Are there caret positions declared for every ligature?
⚠ WARN: Is there kerning info for non-ligated sequences?
⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'.
⚠ WARN: Check for points out of bounds.
  • com.google.fonts/check/points_out_of_bounds
  • ⚠ WARN The following glyphs have coordinates which are out of bounds:
    • ('uni01F1', 22, 590)
    • ('uni01C4', 22, 601)
    • ('Dcaron', 22, 590)
    • ('Dcroat', 22, 590)
    • ('Dcroat.ss02', 22, 590)
    • ('uni01F2', 22, 590)
    • ('uni01C5', 22, 590)
    • ('Ibreve', -27, 819)
    • ('Ibreve', 275, 814)
    • ('uni01E8', 639, 68) and 32 more.
      This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message.

[19] Bellota-BoldItalic.ttf
🔥 FAIL: Checking OS/2 fsType.
  • com.google.fonts/check/fstype
  • 🔥 FAIL OS/2 fsType is a legacy DRM-related field.
    In this font it is set to 8 meaning that:
    The font may be embedded but must only be installed temporarily on other systems.
    No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
    Fonts with this setting indicate that they may be embedded and permanently installed on the remote system by an application.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Copyright notices match canonical pattern in fonts
🔥 FAIL: Checking OS/2 fsSelection value.
🔥 FAIL: Checking head.macStyle value.
🔥 FAIL: Check name table: FONT_FAMILY_NAME entries.
🔥 FAIL: Check name table: FONT_SUBFAMILY_NAME entries.
🔥 FAIL: Check name table: TYPOGRAPHIC_FAMILY_NAME entries.
🔥 FAIL: PPEM must be an integer on hinted fonts.
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
  • com.google.fonts/check/family/win_ascent_and_descent
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 1255, but got 1132 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 396, but got 329 instead [code: descent]
🔥 FAIL: Checking OS/2 Metrics match hhea Metrics.
🔥 FAIL: Whitespace and non-breaking space have the same width?
  • com.google.fonts/check/whitespace_widths
  • 🔥 FAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 312 font units wide, non-breaking space (uni00A0) is 350 font units wide. Both should be positive and the same.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ WARN Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
⚠ WARN: Check if each glyph has the recommended amount of contours.
  • com.google.fonts/check/contour_count
  • ⚠ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:

Glyph name: A Contours detected: 3 Expected: 2
Glyph name: M Contours detected: 3 Expected: 1
Glyph name: f Contours detected: 2 Expected: 1
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: uni20A8 Contours detected: 1 Expected: 3
Glyph name: Agrave Contours detected: 4 Expected: 3
Glyph name: Aacute Contours detected: 4 Expected: 3
Glyph name: Acircumflex Contours detected: 4 Expected: 3
Glyph name: Atilde Contours detected: 4 Expected: 3
Glyph name: Adieresis Contours detected: 5 Expected: 4
Glyph name: Aring Contours detected: 5 Expected: 3 or 4
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Amacron Contours detected: 4 Expected: 3
Glyph name: Abreve Contours detected: 4 Expected: 3
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcommaaccent Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: Wcircumflex Contours detected: 3 Expected: 2
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: uni01CD Contours detected: 4 Expected: 3
Glyph name: uni01DE Contours detected: 6 Expected: 5
Glyph name: uni01E0 Contours detected: 5 Expected: 4
Glyph name: uni01E9 Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: Aringacute Contours detected: 6 Expected: 3, 4 or 5
Glyph name: uni0226 Contours detected: 4 Expected: 3
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni03D6 Contours detected: 1 Expected: 2
Glyph name: Wgrave Contours detected: 3 Expected: 2
Glyph name: Wacute Contours detected: 3 Expected: 2
Glyph name: Wdieresis Contours detected: 4 Expected: 3
Glyph name: uni1EA0 Contours detected: 4 Expected: 3
Glyph name: uni1EA2 Contours detected: 4 Expected: 3
Glyph name: uni1EA4 Contours detected: 5 Expected: 4
Glyph name: uni1EA6 Contours detected: 5 Expected: 4
Glyph name: uni1EA8 Contours detected: 5 Expected: 4
Glyph name: uni1EAA Contours detected: 5 Expected: 4
Glyph name: uni1EAC Contours detected: 5 Expected: 4
Glyph name: uni1EAE Contours detected: 5 Expected: 4
Glyph name: uni1EB0 Contours detected: 5 Expected: 4
Glyph name: uni1EB2 Contours detected: 5 Expected: 4
Glyph name: uni1EB4 Contours detected: 5 Expected: 4
Glyph name: uni1EB6 Contours detected: 5 Expected: 4
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2

⚠ WARN: Are there caret positions declared for every ligature?
⚠ WARN: Is there kerning info for non-ligated sequences?
⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'.
⚠ WARN: Check for points out of bounds.
  • com.google.fonts/check/points_out_of_bounds
  • ⚠ WARN The following glyphs have coordinates which are out of bounds:
    • ('Aacute', -3, 53)
    • ('Abreve', -3, 53)
    • ('uni1EAE', -3, 53)
    • ('uni1EB6', -3, 53)
    • ('uni1EB0', -3, 53)
    • ('uni1EB2', -3, 53)
    • ('uni1EB4', -3, 53)
    • ('uni01CD', -3, 53)
    • ('Acircumflex', -3, 53)
    • ('uni1EA4', -3, 53) and 35 more.
      This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message.

[13] Bellota-Italic.ttf
🔥 FAIL: Checking OS/2 fsType.
  • com.google.fonts/check/fstype
  • 🔥 FAIL OS/2 fsType is a legacy DRM-related field.
    In this font it is set to 8 meaning that:
    The font may be embedded but must only be installed temporarily on other systems.
    No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
    Fonts with this setting indicate that they may be embedded and permanently installed on the remote system by an application.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Copyright notices match canonical pattern in fonts
🔥 FAIL: PPEM must be an integer on hinted fonts.
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
  • com.google.fonts/check/family/win_ascent_and_descent
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 1255, but got 1132 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 396, but got 329 instead [code: descent]
🔥 FAIL: Checking OS/2 Metrics match hhea Metrics.
🔥 FAIL: Whitespace and non-breaking space have the same width?
  • com.google.fonts/check/whitespace_widths
  • 🔥 FAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 291 font units wide, non-breaking space (uni00A0) is 330 font units wide. Both should be positive and the same.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ WARN Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
⚠ WARN: Check if each glyph has the recommended amount of contours.
  • com.google.fonts/check/contour_count
  • ⚠ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:

Glyph name: f Contours detected: 2 Expected: 1
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: uni20A8 Contours detected: 1 Expected: 3
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcommaaccent Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: uni01C6 Contours detected: 3 Expected: 4
Glyph name: uni01E9 Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni03D6 Contours detected: 1 Expected: 2
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2

⚠ WARN: Is there kerning info for non-ligated sequences?
⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'.
⚠ WARN: Check for points out of bounds.
  • com.google.fonts/check/points_out_of_bounds
  • ⚠ WARN The following glyphs have coordinates which are out of bounds:
    • ('dcaron', 661, 713)
    • ('dcaron.ss02', 657, 713)
    • ('lcaron', 315, 709)
    • ('lcaron.ss02', 370, 709)
    • ('napostrophe', 639, 508)
    • ('napostrophe.ss02', 654, 560)
    • ('tcaron', 490, 668)
    • ('tcaron.ss02', 478, 668)
    • ('six.dnom', 168, 311) and ('nine.dnom', 57, 8)
      This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message.

[14] Bellota-Light.ttf
🔥 FAIL: Checking OS/2 fsType.
  • com.google.fonts/check/fstype
  • 🔥 FAIL OS/2 fsType is a legacy DRM-related field.
    In this font it is set to 8 meaning that:
    The font may be embedded but must only be installed temporarily on other systems.
    No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
    Fonts with this setting indicate that they may be embedded and permanently installed on the remote system by an application.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Copyright notices match canonical pattern in fonts
🔥 FAIL: PPEM must be an integer on hinted fonts.
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
  • com.google.fonts/check/family/win_ascent_and_descent
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 1255, but got 1132 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 396, but got 329 instead [code: descent]
🔥 FAIL: Checking OS/2 Metrics match hhea Metrics.
🔥 FAIL: Whitespace and non-breaking space have the same width?
  • com.google.fonts/check/whitespace_widths
  • 🔥 FAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 277 font units wide, non-breaking space (uni00A0) is 317 font units wide. Both should be positive and the same.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ WARN Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
⚠ WARN: Check if each glyph has the recommended amount of contours.
  • com.google.fonts/check/contour_count
  • ⚠ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:

Glyph name: f Contours detected: 2 Expected: 1
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: uni20A8 Contours detected: 1 Expected: 3
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcommaaccent Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: uni01E9 Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni03D6 Contours detected: 1 Expected: 2
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2

⚠ WARN: Are there caret positions declared for every ligature?
⚠ WARN: Is there kerning info for non-ligated sequences?
⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'.
⚠ WARN: Check for points out of bounds.
  • com.google.fonts/check/points_out_of_bounds
  • ⚠ WARN The following glyphs have coordinates which are out of bounds:
    • ('six.dnom', 146, 297) and ('nine.dnom', 85, 4)
      This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message.

[13] Bellota-LightItalic.ttf
🔥 FAIL: Checking OS/2 fsType.
  • com.google.fonts/check/fstype
  • 🔥 FAIL OS/2 fsType is a legacy DRM-related field.
    In this font it is set to 8 meaning that:
    The font may be embedded but must only be installed temporarily on other systems.
    No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
    Fonts with this setting indicate that they may be embedded and permanently installed on the remote system by an application.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Copyright notices match canonical pattern in fonts
🔥 FAIL: PPEM must be an integer on hinted fonts.
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
  • com.google.fonts/check/family/win_ascent_and_descent
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 1255, but got 1132 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 396, but got 329 instead [code: descent]
🔥 FAIL: Checking OS/2 Metrics match hhea Metrics.
🔥 FAIL: Whitespace and non-breaking space have the same width?
  • com.google.fonts/check/whitespace_widths
  • 🔥 FAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 277 font units wide, non-breaking space (uni00A0) is 317 font units wide. Both should be positive and the same.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ WARN Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
⚠ WARN: Check if each glyph has the recommended amount of contours.
  • com.google.fonts/check/contour_count
  • ⚠ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:

Glyph name: f Contours detected: 2 Expected: 1
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: uni20A8 Contours detected: 1 Expected: 3
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcommaaccent Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: Uhorn Contours detected: 2 Expected: 1
Glyph name: uni01C6 Contours detected: 3 Expected: 4
Glyph name: uni01E9 Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni03D6 Contours detected: 1 Expected: 2
Glyph name: uni1EE8 Contours detected: 3 Expected: 2
Glyph name: uni1EEA Contours detected: 3 Expected: 2
Glyph name: uni1EEC Contours detected: 3 Expected: 2
Glyph name: uni1EEE Contours detected: 3 Expected: 2
Glyph name: uni1EF0 Contours detected: 3 Expected: 2
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2

⚠ WARN: Is there kerning info for non-ligated sequences?
⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'.
⚠ WARN: Check for points out of bounds.
  • com.google.fonts/check/points_out_of_bounds
  • ⚠ WARN The following glyphs have coordinates which are out of bounds:
    • ('Cacute.ss02', 667, 639)
    • ('Ccaron.ss02', 667, 639)
    • ('Ccedilla.ss02', 667, 639)
    • ('Ccircumflex.ss02', 667, 639)
    • ('Cdotaccent.ss02', 667, 639)
    • ('uni01CA', -5, 43)
    • ('Nacute', -5, 43)
    • ('Ncaron', -5, 43)
    • ('Ncommaaccent', -5, 43)
    • ('uni01F8', -5, 43) and 13 more.
      This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message.

[14] Bellota-Regular.ttf
🔥 FAIL: Checking OS/2 fsType.
  • com.google.fonts/check/fstype
  • 🔥 FAIL OS/2 fsType is a legacy DRM-related field.
    In this font it is set to 8 meaning that:
    The font may be embedded but must only be installed temporarily on other systems.
    No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
    Fonts with this setting indicate that they may be embedded and permanently installed on the remote system by an application.

More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype

🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Copyright notices match canonical pattern in fonts
🔥 FAIL: PPEM must be an integer on hinted fonts.
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
  • com.google.fonts/check/family/win_ascent_and_descent
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 1255, but got 1132 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 396, but got 329 instead [code: descent]
🔥 FAIL: Checking OS/2 Metrics match hhea Metrics.
🔥 FAIL: Whitespace and non-breaking space have the same width?
  • com.google.fonts/check/whitespace_widths
  • 🔥 FAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 291 font units wide, non-breaking space (uni00A0) is 330 font units wide. Both should be positive and the same.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ WARN Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
⚠ WARN: Check if each glyph has the recommended amount of contours.
  • com.google.fonts/check/contour_count
  • ⚠ WARN This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.

The following glyphs do not have the recommended number of contours:

Glyph name: f Contours detected: 2 Expected: 1
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: uni20A8 Contours detected: 1 Expected: 3
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: Racute Contours detected: 2 Expected: 3
Glyph name: Rcommaaccent Contours detected: 2 Expected: 3
Glyph name: Rcaron Contours detected: 2 Expected: 3
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: uni01E9 Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni03D6 Contours detected: 1 Expected: 2
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2

⚠ WARN: Are there caret positions declared for every ligature?
⚠ WARN: Is there kerning info for non-ligated sequences?
⚠ WARN: Name table strings must not contain the string 'Reserved Font Name'.
⚠ WARN: Check for points out of bounds.
  • com.google.fonts/check/points_out_of_bounds
  • ⚠ WARN The following glyphs have coordinates which are out of bounds:
    • ('six.dnom', 159, 311) and ('nine.dnom', 89, 8)
      This happens a lot when points are not extremes, which is usually bad. However, fixing this alert by adding points on extremes may do more harm than good, especially with italics, calligraphic-script, handwriting, rounded and other fonts. So it is common to ignore this message.

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS
0 57 34 356 37 337
0% 7% 4% 43% 5% 41%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS

Diff images: bellota_qa.zip

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.