I really like the readability of the characters. The kerning and tracking are delightful but even at large font sizes with the largest line spacing setting, there are multiple overlaps. See the example image:
๐ฅFAIL PANOSE proportion is not the same accross this family. In order to fix this, please make sure that the panose.bProportion value is the same in the OS/2 table of all of this family font files.
๐ฅFAIL: Fonts have consistent PANOSE family type?
๐ฅFAIL PANOSE family type is not the same accross this family. In order to fix this, please make sure that the panose.bFamilyType value is the same in the OS/2 table of all of this family font files.
๐ฅFAIL: Fonts have consistent underline thickness?
๐ฅFAIL Thickness of the underline is not the same accross this family. In order to fix this, please make sure that the underlineThickness value is the same in the 'post' table of all of this family font files.
Detected underlineThickness values are:
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-Bold.ttf: 50
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-BoldCondensed.ttf: 50
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-BoldItalic.ttf: 100
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-BoldItalicCondensed.ttf: 100
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-Italic.ttf: 50
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-ItalicCondensed.ttf: 50
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-Regular.ttf: 24
/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-RegularCondensed.ttf: 24
๐ฅFAIL: Verify that each group of fonts with the same nameID 1 has maximum of 4 fonts
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Is 'gasp' table set to optimize rendering?
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2001-2009 by Peter S. Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2001-2009 by Peter S. Baker'
๐ฅFAIL: Check name table: FULL_FONT_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL: Name table entries should not contain line-breaks.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('dollar', 563, -167)
('percent', 549, -95)
('percent', 1338, 1439)
('comma', 122, -384)
('one', 163, 1135)
('two', 903, 280)
('seven', 65, 995)
('nine', 196, -49)
('semicolon', 196, -384)
('C', 1321, 342) and 198 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.
[21] Junicode-BoldCondensed.ttf๐ฅFAIL: Checking file is named canonically.
๐ฅFAIL Style name used in "/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-BoldCondensed.ttf" is not canonical. You should rebuild the font using any of the following style names: "Thin", "ExtraLight", "Light", "Regular", "Medium", "SemiBold", "Bold", "ExtraBold", "Black", "Thin Italic", "ExtraLight Italic", "Light Italic", "Italic", "Medium Italic", "SemiBold Italic", "Bold Italic", "ExtraBold Italic", "Black Italic".
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Copyright notices match canonical pattern in fonts
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2001-2009 by Peter S. Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2001-2009 by Peter S. Baker'
๐ฅFAIL: Check name table: FONT_SUBFAMILY_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL: Name table entries should not contain line-breaks.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('dollar', 450, -167)
('percent', 439, -95)
('percent', 1070, 1439)
('comma', 98, -384)
('one', 130, 1135)
('two', 722, 280)
('seven', 52, 995)
('nine', 157, -49)
('semicolon', 157, -384)
('C', 1057, 342) and 190 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.
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Is 'gasp' table set to optimize rendering?
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2003-2009 by Peter Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2003-2009 by Peter Baker'
๐ฅFAIL: Check name table: FONT_SUBFAMILY_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL: Name table entries should not contain line-breaks.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
๐ฅFAIL: Whitespace and non-breaking space have the same width?
๐ฅFAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 559 font units wide, non-breaking space (uni00A0) is 4194 font units wide. Both should be positive and the same.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('dollar', 71, 236)
('quotesingle', 705, 1481)
('parenleft', 469, -360)
('parenleft', 147, 584)
('parenleft', 909, 1532)
('parenleft', 946, 1487)
('parenright', 664, 586)
('parenright', -94, -362)
('parenright', -137, -315)
('parenright', 342, 1532) and 283 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.
[22] Junicode-BoldItalicCondensed.ttf๐ฅFAIL: Checking file is named canonically.
๐ฅFAIL Style name used in "/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-BoldItalicCondensed.ttf" is not canonical. You should rebuild the font using any of the following style names: "Thin", "ExtraLight", "Light", "Regular", "Medium", "SemiBold", "Bold", "ExtraBold", "Black", "Thin Italic", "ExtraLight Italic", "Light Italic", "Italic", "Medium Italic", "SemiBold Italic", "Bold Italic", "ExtraBold Italic", "Black Italic".
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Copyright notices match canonical pattern in fonts
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2003-2009 by Peter Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2003-2009 by Peter Baker'
๐ฅFAIL: Check name table: FONT_SUBFAMILY_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL: Name table entries should not contain line-breaks.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
๐ฅFAIL: Whitespace and non-breaking space have the same width?
๐ฅFAIL Whitespace and non-breaking space have differing width: Whitespace (space) is 447 font units wide, non-breaking space (uni00A0) is 3355 font units wide. Both should be positive and the same.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('dollar', 57, 236)
('quotesingle', 564, 1481)
('parenleft', 375, -360)
('parenleft', 118, 584)
('parenleft', 727, 1532)
('parenleft', 757, 1487)
('parenright', 531, 586)
('parenright', -75, -362)
('parenright', -110, -315)
('parenright', 274, 1532) and 279 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.
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Is 'gasp' table set to optimize rendering?
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2002-2009 by Peter S. Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2002-2009 by Peter S. Baker'
๐ฅFAIL: Check name table: FULL_FONT_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL The following glyph names do not comply with naming conventions: uniF1C3#1
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.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('parenleft', 383, -356)
('parenleft', 940, 1510)
('parenright', -191, -330)
('six', 1050, 1382)
('nine', 96, 22)
('Q', 1492, -361)
('Z', 1039, -36)
('Z', 400, 1370)
('a', 886, 882)
('k', 77, -27) and 275 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.
[23] Junicode-ItalicCondensed.ttf๐ฅFAIL: Checking file is named canonically.
๐ฅFAIL Style name used in "/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-ItalicCondensed.ttf" is not canonical. You should rebuild the font using any of the following style names: "Thin", "ExtraLight", "Light", "Regular", "Medium", "SemiBold", "Bold", "ExtraBold", "Black", "Thin Italic", "ExtraLight Italic", "Light Italic", "Italic", "Medium Italic", "SemiBold Italic", "Bold Italic", "ExtraBold Italic", "Black Italic".
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Copyright notices match canonical pattern in fonts
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2002-2009 by Peter S. Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 2002-2009 by Peter S. Baker'
๐ฅFAIL: Check name table: FONT_SUBFAMILY_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL The following glyph names do not comply with naming conventions: uniF1C3#1
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.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('parenleft', 307, -356)
('parenleft', 752, 1510)
('six', 840, 1382)
('Q', 1194, -361)
('Z', 831, -36)
('Z', 320, 1370)
('a', 709, 882)
('k', 61, -27)
('l', 440, 1484)
('m', 83, -27) and 253 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.
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Is 'gasp' table set to optimize rendering?
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 1998-2009 by Peter S. Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 1998-2009 by Peter S. Baker'
๐ฅFAIL: Check name table: FULL_FONT_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL: Name table entries should not contain line-breaks.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('Q', 1662, -364)
('d', 990, 32)
('z', 103, 873)
('z', 714, 284)
('currency', 77, 1019)
('currency', 161, 1103)
('currency', 863, 1103)
('currency', 947, 1019)
('currency', 948, 316)
('currency', 76, 316) and 349 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.
[21] Junicode-RegularCondensed.ttf๐ฅFAIL: Checking file is named canonically.
๐ฅFAIL Style name used in "/var/folders/y0/gs7dshh54gng8n1zgzr53nbw0000gn/T/tmpltbgommp/Junicode-RegularCondensed.ttf" is not canonical. You should rebuild the font using any of the following style names: "Thin", "ExtraLight", "Light", "Regular", "Medium", "SemiBold", "Bold", "ExtraBold", "Black", "Thin Italic", "ExtraLight Italic", "Light Italic", "Italic", "Medium Italic", "SemiBold Italic", "Bold Italic", "ExtraBold Italic", "Black Italic".
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y between 1.000 and 9.999. Current version string is: "Version 0.6.17 " [code: bad-version-strings]
๐ฅFAIL: Copyright notices match canonical pattern in fonts
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 1998-2009 by Peter S. Baker'
๐ฅFAIL Name Table entry: Copyright notices should match a pattern similar to: 'Copyright 2017 The Familyname Project Authors (git url)'
But instead we have got: 'Copyright (c) 1998-2009 by Peter S. Baker'
๐ฅFAIL: Check name table: FONT_SUBFAMILY_NAME entries.
๐ฅFAIL 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script.
๐ฅFAIL: Name table records must not have trailing spaces.
๐ฅFAIL Unwanted tables were found in the font and should be removed, either by fonttools/ttx or by editing them using the tool they are from: FFTM (from FontForge)
๐ฅFAIL: Name table entries should not contain line-breaks.
๐ฅFAIL This font lacks a digital signature (DSIG table). Some applications may require one (even if only a dummy placeholder) in order to work properly. You can add a DSIG table by running the gftools fix-dsig script.
โ WARN Even though unitsPerEm (2048) 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.
โ 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:
โ WARN The following glyphs have coordinates which are out of bounds:
('Q', 1330, -364)
('d', 792, 32)
('z', 82, 873)
('currency', 62, 1019)
('currency', 129, 1103)
('currency', 690, 1103)
('currency', 758, 1019)
('currency', 758, 316)
('currency', 61, 316)
('guillemotleft', 315, 58) and 299 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.
Summary
๐ ERROR
๐ฅ FAIL
โ WARN
๐ค SKIP
โน INFO
๐ PASS
0
111
60
498
45
369
0%
10%
6%
46%
4%
34%
Note: The following loglevels were omitted in this report: