noponies/turret-road

A free, angular sans serif typeface

turret-road's Issues

Migrate to interpolated multiple master

Migrate seperate glyphs files into single multiple master for extra interpolated weights.

Google Fonts QA report

Fontbakery report

Fontbakery version: 0.7.8

[1] Family checks

🔥 FAIL: Verify that each group of fonts with the same nameID 1 has maximum of 4 fonts

• com.adobe.fonts/check/family/max_4_fonts_per_family_name
• 🔥 FAIL Family 'Turret Road' has 6 fonts (should be 4 or fewer).

[8] TurretRoad-Bold.ttf

🔥 FAIL: Check glyph coverage.

• com.google.fonts/check/glyph_coverage
• 🔥 FAIL Missing required codepoints: 0x2215 (DIVISION SLASH)

🔥 FAIL: PPEM must be an integer on hinted fonts.

• com.google.fonts/check/integer_ppem_if_hinted
• 🔥 FAIL This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into and integer value.

⚠ WARN: Font has old ttfautohint applied?

• com.google.fonts/check/old_ttfautohint
• ⚠ WARN ttfautohint used in font = 1.8; installed = 1.8.3; Need to re-run with the newer version!

⚠ 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: germandbls Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 1 Expected: 2
Glyph name: greaterequal Contours detected: 1 Expected: 2
Glyph name: uni2158 Contours detected: 3 Expected: 4

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

• com.google.fonts/check/ligature_carets
• ⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

• com.google.fonts/check/kerning_for_non_ligated_sequences

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

  • f + i
  • i + l

  [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.

• com.google.fonts/check/linegaps
• ⚠ WARN hhea lineGap is not equal to 0. [code: hhea]

[9] TurretRoad-ExtraBold.ttf

🔥 FAIL: Check glyph coverage.

• com.google.fonts/check/glyph_coverage
• 🔥 FAIL Missing required codepoints: 0x2215 (DIVISION SLASH)

🔥 FAIL: PPEM must be an integer on hinted fonts.

• com.google.fonts/check/integer_ppem_if_hinted
• 🔥 FAIL This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into and integer value.

⚠ WARN: Font has old ttfautohint applied?

• com.google.fonts/check/old_ttfautohint
• ⚠ WARN ttfautohint used in font = 1.8; installed = 1.8.3; Need to re-run with the newer version!

⚠ 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: germandbls Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 1 Expected: 2
Glyph name: greaterequal Contours detected: 1 Expected: 2
Glyph name: uni2158 Contours detected: 3 Expected: 4

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

• com.google.fonts/check/ligature_carets
• ⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

• com.google.fonts/check/kerning_for_non_ligated_sequences

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

  • f + i
  • i + l

  [code: lacks-kern-info]

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

• com.google.fonts/check/name/family_and_style_max_length
• ⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries: FONT_FAMILY_NAME = 'Turret Road ExtraBold' / SUBFAMILY_NAME = 'Regular'
• ⚠ WARN Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behing these name table records max-length criteria.

⚠ WARN: Checking Vertical Metric Linegaps.

• com.google.fonts/check/linegaps
• ⚠ WARN hhea lineGap is not equal to 0. [code: hhea]

[10] TurretRoad-ExtraLight.ttf

🔥 FAIL: Check glyph coverage.

• com.google.fonts/check/glyph_coverage
• 🔥 FAIL Missing required codepoints: 0x2215 (DIVISION SLASH)

🔥 FAIL: PPEM must be an integer on hinted fonts.

• com.google.fonts/check/integer_ppem_if_hinted
• 🔥 FAIL This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into and integer value.

⚠ WARN: Checking OS/2 usWeightClass.

• com.google.fonts/check/usweightclass
• ⚠ WARN {}:{} is OK on TTFs, but OTF files with those values will cause bluring on Windows. GlyphsApp users must set a Instance Custom Parameter for the Thin and ExtraLight styles to 250 and 275, so that if OTFs are exported then it will not blur on Windows.

⚠ WARN: Font has old ttfautohint applied?

• com.google.fonts/check/old_ttfautohint
• ⚠ WARN ttfautohint used in font = 1.8; installed = 1.8.3; Need to re-run with the newer version!

⚠ 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: AE Contours detected: 4 Expected: 2
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 1 Expected: 2
Glyph name: greaterequal Contours detected: 1 Expected: 2
Glyph name: uni2158 Contours detected: 3 Expected: 4

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

• com.google.fonts/check/ligature_carets
• ⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

• com.google.fonts/check/kerning_for_non_ligated_sequences

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

  • f + i
  • i + l

  [code: lacks-kern-info]

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

• com.google.fonts/check/name/family_and_style_max_length
• ⚠ WARN The combined length of family and style exceeds 27 chars in the following 'WINDOWS' entries: FONT_FAMILY_NAME = 'Turret Road ExtraLight' / SUBFAMILY_NAME = 'Regular'
• ⚠ WARN Please take a look at the conversation at fonttools/fontbakery#2179 in order to understand the reasoning behing these name table records max-length criteria.

⚠ WARN: Checking Vertical Metric Linegaps.

• com.google.fonts/check/linegaps
• ⚠ WARN hhea lineGap is not equal to 0. [code: hhea]

[8] TurretRoad-Light.ttf

🔥 FAIL: Check glyph coverage.

• com.google.fonts/check/glyph_coverage
• 🔥 FAIL Missing required codepoints: 0x2215 (DIVISION SLASH)

🔥 FAIL: PPEM must be an integer on hinted fonts.

• com.google.fonts/check/integer_ppem_if_hinted
• 🔥 FAIL This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into and integer value.

⚠ WARN: Font has old ttfautohint applied?

• com.google.fonts/check/old_ttfautohint
• ⚠ WARN ttfautohint used in font = 1.8; installed = 1.8.3; Need to re-run with the newer version!

⚠ 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: germandbls Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 1 Expected: 2
Glyph name: greaterequal Contours detected: 1 Expected: 2
Glyph name: uni2158 Contours detected: 3 Expected: 4

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

• com.google.fonts/check/ligature_carets
• ⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

• com.google.fonts/check/kerning_for_non_ligated_sequences

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

  • f + i
  • i + l

  [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.

• com.google.fonts/check/linegaps
• ⚠ WARN hhea lineGap is not equal to 0. [code: hhea]

[8] TurretRoad-Medium.ttf

🔥 FAIL: Check glyph coverage.

• com.google.fonts/check/glyph_coverage
• 🔥 FAIL Missing required codepoints: 0x2215 (DIVISION SLASH)

🔥 FAIL: PPEM must be an integer on hinted fonts.

• com.google.fonts/check/integer_ppem_if_hinted
• 🔥 FAIL This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into and integer value.

⚠ WARN: Font has old ttfautohint applied?

• com.google.fonts/check/old_ttfautohint
• ⚠ WARN ttfautohint used in font = 1.8; installed = 1.8.3; Need to re-run with the newer version!

⚠ 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: germandbls Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 1 Expected: 2
Glyph name: greaterequal Contours detected: 1 Expected: 2
Glyph name: uni2158 Contours detected: 3 Expected: 4

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

• com.google.fonts/check/ligature_carets
• ⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

• com.google.fonts/check/kerning_for_non_ligated_sequences

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

  • f + i
  • i + l

  [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.

• com.google.fonts/check/linegaps
• ⚠ WARN hhea lineGap is not equal to 0. [code: hhea]

[8] TurretRoad-Regular.ttf

🔥 FAIL: Check glyph coverage.

• com.google.fonts/check/glyph_coverage
• 🔥 FAIL Missing required codepoints: 0x2215 (DIVISION SLASH)

🔥 FAIL: PPEM must be an integer on hinted fonts.

• com.google.fonts/check/integer_ppem_if_hinted
• 🔥 FAIL This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into and integer value.

⚠ WARN: Font has old ttfautohint applied?

• com.google.fonts/check/old_ttfautohint
• ⚠ WARN ttfautohint used in font = 1.8; installed = 1.8.3; Need to re-run with the newer version!

⚠ 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: germandbls Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 1 Expected: 2
Glyph name: greaterequal Contours detected: 1 Expected: 2
Glyph name: uni2158 Contours detected: 3 Expected: 4

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

• com.google.fonts/check/ligature_carets
• ⚠ WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

• com.google.fonts/check/kerning_for_non_ligated_sequences

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

  • f + i
  • i + l

  [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.

• com.google.fonts/check/linegaps
• ⚠ WARN hhea lineGap is not equal to 0. [code: hhea]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS
0	13	39	356	31	382
0%	2%	5%	43%	4%	47%

Note: The following loglevels were omitted in this report:

• SKIP
• INFO
• PASS

Diff images: turret_road_qa.zip

Add oblique style

Add oblique style for each weight in Turret Road.