[8] TitilliumWeb-Roman-VF.ttf:fire: FAIL: Glyph names are all valid?
* [com.google.fonts/check/058](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :fire: **FAIL** The following glyph names do not comply with naming conventions: ['alefMaksura_alefMaksuraar.fina.alt', 'yehHamzaabove_yehHamzaabovear.fina'] A glyph name may be up to 31 characters in length, must be entirely comprised of characters from the following set: A-Z a-z 0-9 .(period) _(underscore). and must not start with a digit or period. There are a few exceptions such as the special character ".notdef". The glyph names "twocents", "a1", and "_" are all valid, while "2cents" and ".twocents" are not.
:fire: FAIL: The variable font 'wght' (Weight) axis coordinate must be 400 on the 'Regular' instance.
* [com.google.fonts/check/167](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :fire: **FAIL** The 'wght' axis coordinate of the 'Regular' instance must be 400. Got a '361.61617' coordinate instead.
:fire: FAIL: The variable font 'wght' (Weight) axis coordinate must be 700 on the 'Bold' instance.
* [com.google.fonts/check/172](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :fire: **FAIL** The 'wght' axis coordinate of the 'Bold' instance must be 700. Got a '600.0' coordinate instead.
:warning: WARN: Stricter unitsPerEm criteria for Google Fonts.
* [com.google.fonts/check/116](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :warning: **WARN** Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will liely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.
:warning: WARN: Check if each glyph has the recommended amount of contours.
* [com.google.fonts/check/153](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :warning: **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: currency Contours detected: 6 Expected: 2
Glyph name: Euro Contours detected: 3 Expected: 1 or 2
Glyph name: uni03BC Contours detected: 2 Expected: 1
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Oslash Contours detected: 4 Expected: 3
Glyph name: eth Contours detected: 3 Expected: 2
Glyph name: oslash Contours detected: 4 Expected: 3
Glyph name: aogonek Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: eogonek Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: lslash Contours detected: 2 Expected: 1
Glyph name: Eng Contours detected: 2 Expected: 1
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: tbar Contours detected: 2 Expected: 1
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: uogonek Contours detected: 2 Expected: 1
Glyph name: Oslashacute Contours detected: 5 Expected: 4
Glyph name: oslashacute Contours detected: 5 Expected: 4
Glyph name: radical Contours detected: 2 Expected: 1
Glyph name: infinity Contours detected: 4 Expected: 3
Glyph name: notequal Contours detected: 3 Expected: 1
Glyph name: pi Contours detected: 3 Expected: 1
:warning: WARN: Font contains .notdef as first glyph?
* [com.google.fonts/check/046](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :warning: **WARN** Font should contain the .notdef glyph as the first glyph, it should not have a Unicode value assigned and should contain a drawing.
:warning: WARN: Does GPOS table have kerning information?
* [com.google.fonts/check/063](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :warning: **WARN** GPOS table lacks kerning information.
:warning: WARN: Check for points out of bounds.
* [com.google.fonts/check/075](https://github.com/googlefonts/fontbakery/search?q={checkid})
* :warning: **WARN** The following glyphs have coordinates which are out of bounds:
[('uni066C', 44.0572, -122.4099), ('uni066C', 75.6118, 35.3631), ('uni066C', 105.6638, 35.3631), ('uni066C', 67.3475, -122.4099), ('quotesinglbase', 121.2, 114.85), ('quotedblbase', 247.2, 108.85), ('quotedblleft', 273.14588, 727.1452), ('quotedblleft', 243.65775, 727.1452), ('quotedblleft', 140.14588, 727.1452), ('quotedblleft', 110.65775, 727.1452), ('quotedblright', 62.85412, 526.8548), ('quotedblright', 92.34225, 526.8548), ('quotedblright', 206.85412, 526.8548), ('quotedblright', 236.34225, 526.8548), ('quoteleft', 140.2, 726.85), ('quoteright', 62.8, 527.15), ('approxequal', 492.465, 329.0), ('approxequal', 492.465, 167.0)]
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
:broken_heart: ERROR
:fire: FAIL
:warning: WARN
:zzz: SKIP
:information_source: INFO
:bread: PASS
0
3
5
64
6
60
0%
2%
4%
46%
4%
43%
Note: The following loglevels were omitted in this report:
SKIP
INFO
PASS
When compared against current GF version:
2 Glyphs names are too long
Font weights are diff (we've talked about this before) @davelab6, we'll release this at your discretion. It's requested 765m times a week, people will complain.
Some glyph interpolation issues
remove MVAR table
Family names are incorrect. Cairo is used for Typographic Family Name (named ID16) in Roman.
Fontbakery report
Fontbakery version: 0.6.4
[8] TitilliumWeb-Roman-VF.ttf
:fire: FAIL: Glyph names are all valid?
* [com.google.fonts/check/058](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :fire: **FAIL** The following glyph names do not comply with naming conventions: ['alefMaksura_alefMaksuraar.fina.alt', 'yehHamzaabove_yehHamzaabovear.fina'] A glyph name may be up to 31 characters in length, must be entirely comprised of characters from the following set: A-Z a-z 0-9 .(period) _(underscore). and must not start with a digit or period. There are a few exceptions such as the special character ".notdef". The glyph names "twocents", "a1", and "_" are all valid, while "2cents" and ".twocents" are not.:fire: FAIL: The variable font 'wght' (Weight) axis coordinate must be 400 on the 'Regular' instance.
* [com.google.fonts/check/167](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :fire: **FAIL** The 'wght' axis coordinate of the 'Regular' instance must be 400. Got a '361.61617' coordinate instead.:fire: FAIL: The variable font 'wght' (Weight) axis coordinate must be 700 on the 'Bold' instance.
* [com.google.fonts/check/172](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :fire: **FAIL** The 'wght' axis coordinate of the 'Bold' instance must be 700. Got a '600.0' coordinate instead.:warning: WARN: Stricter unitsPerEm criteria for Google Fonts.
* [com.google.fonts/check/116](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :warning: **WARN** Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will liely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations.:warning: WARN: Check if each glyph has the recommended amount of contours.
* [com.google.fonts/check/153](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :warning: **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: currency Contours detected: 6 Expected: 2 Glyph name: Euro Contours detected: 3 Expected: 1 or 2 Glyph name: uni03BC Contours detected: 2 Expected: 1 Glyph name: Eth Contours detected: 3 Expected: 2 Glyph name: Oslash Contours detected: 4 Expected: 3 Glyph name: eth Contours detected: 3 Expected: 2 Glyph name: oslash Contours detected: 4 Expected: 3 Glyph name: aogonek Contours detected: 3 Expected: 2 Glyph name: Dcroat Contours detected: 3 Expected: 2 Glyph name: dcroat Contours detected: 3 Expected: 2 Glyph name: eogonek Contours detected: 3 Expected: 2 Glyph name: hbar Contours detected: 2 Expected: 1 Glyph name: Lslash Contours detected: 2 Expected: 1 Glyph name: lslash Contours detected: 2 Expected: 1 Glyph name: Eng Contours detected: 2 Expected: 1 Glyph name: Tbar Contours detected: 2 Expected: 1 Glyph name: tbar Contours detected: 2 Expected: 1 Glyph name: Uogonek Contours detected: 2 Expected: 1 Glyph name: uogonek Contours detected: 2 Expected: 1 Glyph name: Oslashacute Contours detected: 5 Expected: 4 Glyph name: oslashacute Contours detected: 5 Expected: 4 Glyph name: radical Contours detected: 2 Expected: 1 Glyph name: infinity Contours detected: 4 Expected: 3 Glyph name: notequal Contours detected: 3 Expected: 1 Glyph name: pi Contours detected: 3 Expected: 1:warning: WARN: Font contains .notdef as first glyph?
* [com.google.fonts/check/046](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :warning: **WARN** Font should contain the .notdef glyph as the first glyph, it should not have a Unicode value assigned and should contain a drawing.:warning: WARN: Does GPOS table have kerning information?
* [com.google.fonts/check/063](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :warning: **WARN** GPOS table lacks kerning information.:warning: WARN: Check for points out of bounds.
* [com.google.fonts/check/075](https://github.com/googlefonts/fontbakery/search?q={checkid}) * :warning: **WARN** The following glyphs have coordinates which are out of bounds: [('uni066C', 44.0572, -122.4099), ('uni066C', 75.6118, 35.3631), ('uni066C', 105.6638, 35.3631), ('uni066C', 67.3475, -122.4099), ('quotesinglbase', 121.2, 114.85), ('quotedblbase', 247.2, 108.85), ('quotedblleft', 273.14588, 727.1452), ('quotedblleft', 243.65775, 727.1452), ('quotedblleft', 140.14588, 727.1452), ('quotedblleft', 110.65775, 727.1452), ('quotedblright', 62.85412, 526.8548), ('quotedblright', 92.34225, 526.8548), ('quotedblright', 206.85412, 526.8548), ('quotedblright', 236.34225, 526.8548), ('quoteleft', 140.2, 726.85), ('quoteright', 62.8, 527.15), ('approxequal', 492.465, 329.0), ('approxequal', 492.465, 167.0)] 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 messageSummary
Note: The following loglevels were omitted in this report:
When compared against current GF version: