Giter Site home page Giter Site logo

junicode's People

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 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 avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar

Forkers

bghryct m4rc1e seyisulu

junicode's Issues

Leading is too small for kindle.

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:
JunicodeIssue

Google Fonts QA report

Fontbakery report

Fontbakery version: 0.7.9

[4] Family checks
🔥 FAIL: Fonts have consistent PANOSE proportion?
  • com.google.fonts/check/family/panose_proportion
  • 🔥 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?
  • com.google.fonts/check/family/panose_familytype
  • 🔥 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?
  • com.google.fonts/check/family/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

[19] Junicode-Bold.ttf
🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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: Copyright notices match canonical pattern in fonts
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/fullfontname
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):MACINTOSH(1)] on the 'name' table: Expected 'Junicode Bold' but got 'JunicodeBold'.
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):WINDOWS(3)] on the 'name' table: Expected 'Junicode Bold' but got 'JunicodeBold'.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: aogonek Contours detected: 3 Expected: 2
Glyph name: uni01E5 Contours detected: 4 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0229 Contours detected: 3 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 positioning values for these ligature glyphs:

    • ellipsis
    • ij
    • IJ
    • f_nordicthorn
    • f_eth
    • f_thorn

    [code: incomplete-caret-pos-data]

⚠ 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:

    • period + period
    • f + thorn
    • thorn + eth
    • eth + j
    • j + nordiceth
    • nordiceth + nordicthorn
    • nordicthorn + f
    • f + l
    • l + i
    • longs + b
    • b + i
    • i + k
    • k + h
    • h + l
    • l + longs
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • l + j
    • n + j

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.
  • com.google.fonts/check/canonical_filename
  • 🔥 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: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/subfamilyname
  • 🔥 FAIL SUBFAMILY_NAME for Mac "BoldCondensed" must be "Condensed Bold" [code: bad-familyname]
  • 🔥 FAIL SUBFAMILY_NAME for Win "BoldCondensed" must be "Regular" [code: bad-familyname]
🔥 FAIL: Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Is 'gasp' table set to optimize rendering?
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: aogonek Contours detected: 3 Expected: 2
Glyph name: uni01E5 Contours detected: 4 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0229 Contours detected: 3 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 positioning values for these ligature glyphs:

    • ellipsis
    • ij
    • IJ
    • f_nordicthorn
    • f_eth
    • f_thorn

    [code: incomplete-caret-pos-data]

⚠ 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:

    • period + period
    • f + thorn
    • thorn + eth
    • eth + j
    • j + nordiceth
    • nordiceth + nordicthorn
    • nordicthorn + f
    • f + l
    • l + i
    • longs + b
    • b + i
    • i + k
    • k + h
    • h + l
    • l + longs
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • l + j
    • n + j

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.

[21] Junicode-BoldItalic.ttf
🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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: Copyright notices match canonical pattern in fonts
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/subfamilyname
  • 🔥 FAIL SUBFAMILY_NAME for Mac "BoldItalic" must be "Bold Italic" [code: bad-familyname]
  • 🔥 FAIL SUBFAMILY_NAME for Win "BoldItalic" must be "Bold Italic" [code: bad-familyname]
🔥 FAIL: Check name table: FULL_FONT_NAME entries.
  • com.google.fonts/check/name/fullfontname
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):MACINTOSH(1)] on the 'name' table: Expected 'Junicode Bold Italic' but got 'JunicodeBoldItalic'.
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):WINDOWS(3)] on the 'name' table: Expected 'Junicode Bold Italic' but got 'JunicodeBoldItalic'.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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?
  • com.google.fonts/check/whitespace_widths
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: percent Contours detected: 4 Expected: 5
Glyph name: aogonek Contours detected: 3 Expected: 2
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: uogonek Contours detected: 2 Expected: 1
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: uni0229 Contours detected: 3 Expected: 2
Glyph name: uniFB00 Contours detected: 3 Expected: 1 or 2
Glyph name: uniFB04 Contours detected: 4 Expected: 1, 2 or 3

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

  • com.google.fonts/check/ligature_carets

  • ⚠ WARN This font lacks caret positioning values for these ligature glyphs:

    • uni01F2
    • uni01C8
    • uni01C9
    • uni01C6
    • uni01CB
    • uni01C4
    • ellipsis
    • uni01CA
    • ij
    • uni01F3
    • IJ
    • f_eth
    • f_nordicthorn
    • f_thorn
    • uni01C7
    • uni01C5
    • uni01CC
    • uni01F1

    [code: incomplete-caret-pos-data]

⚠ 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:

    • period + period
    • f + eth
    • eth + j
    • j + nordicthorn
    • nordicthorn + thorn
    • thorn + l
    • l + i
    • i + f
    • longs + i
    • i + b
    • b + k
    • k + h
    • h + l
    • l + longs
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • l + j
    • n + j

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.
  • com.google.fonts/check/canonical_filename
  • 🔥 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: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/subfamilyname
  • 🔥 FAIL SUBFAMILY_NAME for Mac "BoldItalicCondensed" must be "Condensed Bold Italic" [code: bad-familyname]
  • 🔥 FAIL SUBFAMILY_NAME for Win "BoldItalicCondensed" must be "Italic" [code: bad-familyname]
🔥 FAIL: Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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?
  • com.google.fonts/check/whitespace_widths
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Is 'gasp' table set to optimize rendering?
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: percent Contours detected: 4 Expected: 5
Glyph name: aogonek Contours detected: 3 Expected: 2
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: uogonek Contours detected: 2 Expected: 1
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: uni0229 Contours detected: 3 Expected: 2
Glyph name: uniFB00 Contours detected: 3 Expected: 1 or 2
Glyph name: uniFB04 Contours detected: 4 Expected: 1, 2 or 3

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

  • com.google.fonts/check/ligature_carets

  • ⚠ WARN This font lacks caret positioning values for these ligature glyphs:

    • uni01F2
    • uni01C8
    • uni01C9
    • uni01C6
    • uni01CB
    • uni01C4
    • ellipsis
    • uni01CA
    • ij
    • uni01F3
    • IJ
    • f_eth
    • f_nordicthorn
    • f_thorn
    • uni01C7
    • uni01C5
    • uni01CC
    • uni01F1

    [code: incomplete-caret-pos-data]

⚠ 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:

    • period + period
    • f + eth
    • eth + j
    • j + nordicthorn
    • nordicthorn + thorn
    • thorn + l
    • l + i
    • i + f
    • longs + i
    • i + b
    • b + k
    • k + h
    • h + l
    • l + longs
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • l + j
    • n + j

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.

[21] Junicode-Italic.ttf
🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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: Copyright notices match canonical pattern in fonts
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/fullfontname
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):MACINTOSH(1)] on the 'name' table: Expected 'Junicode Italic' but got 'JunicodeItalic'.
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):WINDOWS(3)] on the 'name' table: Expected 'Junicode Italic' but got 'JunicodeItalic'.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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: Glyph names are all valid?

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: Font contains unique glyph names?
🔥 FAIL: Name table entries should not contain line-breaks.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: aogonek Contours detected: 3 Expected: 2
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: uogonek Contours detected: 2 Expected: 1
Glyph name: uni0199 Contours detected: 2 Expected: 1
Glyph name: uni01E5 Contours detected: 4 Expected: 2
Glyph name: kcaron Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0229 Contours detected: 3 Expected: 2
Glyph name: percent Contours detected: 4 Expected: 5
Glyph name: uni03D7 Contours detected: 2 Expected: 1
Glyph name: uni1E08 Contours detected: 3 Expected: 2
Glyph name: uni1E09 Contours detected: 3 Expected: 2
Glyph name: uni1E1C Contours detected: 3 Expected: 2
Glyph name: uni1E1D Contours detected: 4 Expected: 3
Glyph name: uniEFFD Contours detected: 4 Expected: 9 or 7

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

  • com.google.fonts/check/ligature_carets

  • ⚠ WARN This font lacks caret positioning values for these ligature glyphs:

    • jcircumflex
    • ellipsis
    • f_eth
    • f_nordicthorn
    • f_thorn
    • second

    [code: incomplete-caret-pos-data]

⚠ 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:

    • period + period
    • f + nordicthorn
    • nordicthorn + thorn
    • thorn + j
    • j + nordiceth
    • nordiceth + eth
    • eth + l
    • l + i
    • i + f
    • slong + b
    • b + i
    • i + k
    • k + h
    • h + l
    • l + slong
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • j + circumflexnosp
    • l + j
    • n + j
    • prime1 + prime1

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.
  • com.google.fonts/check/canonical_filename
  • 🔥 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: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/subfamilyname
  • 🔥 FAIL SUBFAMILY_NAME for Mac "ItalicCondensed" must be "Condensed Italic" [code: bad-familyname]
  • 🔥 FAIL SUBFAMILY_NAME for Win "ItalicCondensed" must be "Italic" [code: bad-familyname]
🔥 FAIL: Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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: Glyph names are all valid?

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: Font contains unique glyph names?
🔥 FAIL: Name table entries should not contain line-breaks.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Is 'gasp' table set to optimize rendering?
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: aogonek Contours detected: 3 Expected: 2
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: uogonek Contours detected: 2 Expected: 1
Glyph name: uni0199 Contours detected: 2 Expected: 1
Glyph name: uni01E5 Contours detected: 4 Expected: 2
Glyph name: kcaron Contours detected: 3 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0229 Contours detected: 3 Expected: 2
Glyph name: percent Contours detected: 4 Expected: 5
Glyph name: uni03D7 Contours detected: 2 Expected: 1
Glyph name: uni1E08 Contours detected: 3 Expected: 2
Glyph name: uni1E09 Contours detected: 3 Expected: 2
Glyph name: uni1E1C Contours detected: 3 Expected: 2
Glyph name: uni1E1D Contours detected: 4 Expected: 3
Glyph name: uniEFFD Contours detected: 4 Expected: 9 or 7

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

  • com.google.fonts/check/ligature_carets

  • ⚠ WARN This font lacks caret positioning values for these ligature glyphs:

    • jcircumflex
    • ellipsis
    • f_eth
    • f_nordicthorn
    • f_thorn
    • second

    [code: incomplete-caret-pos-data]

⚠ 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:

    • period + period
    • f + nordicthorn
    • nordicthorn + thorn
    • thorn + j
    • j + nordiceth
    • nordiceth + eth
    • eth + l
    • l + i
    • i + f
    • slong + b
    • b + i
    • i + k
    • k + h
    • h + l
    • l + slong
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • j + circumflexnosp
    • l + j
    • n + j
    • prime1 + prime1

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.

[19] Junicode-Regular.ttf
🔥 FAIL: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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: Copyright notices match canonical pattern in fonts
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/fullfontname
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):MACINTOSH(1)] on the 'name' table: Expected 'Junicode Regular' but got 'JunicodeRegular'.
  • 🔥 FAIL Entry [FULL_FONT_NAME(4):WINDOWS(3)] on the 'name' table: Expected 'Junicode Regular' but got 'JunicodeRegular'.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: aogonek Contours detected: 3 Expected: 2
Glyph name: uni01BB Contours detected: 2 Expected: 1
Glyph name: uni01C2 Contours detected: 3 Expected: 1
Glyph name: uni01E5 Contours detected: 4 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0229 Contours detected: 3 Expected: 2
Glyph name: uni203D Contours detected: 3 Expected: 2
Glyph name: uni03D7 Contours detected: 2 Expected: 1
Glyph name: uniF200 Contours detected: 2 Expected: 14
Glyph name: Ccedillaacute Contours detected: 3 Expected: 2
Glyph name: ccedillaacute Contours detected: 3 Expected: 2
Glyph name: Ecedillabreve Contours detected: 3 Expected: 2
Glyph name: ecedillabreve Contours detected: 4 Expected: 3
Glyph name: uni2158 Contours detected: 3 Expected: 4
Glyph name: uniEFFD Contours detected: 4 Expected: 9 or 7

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

  • com.google.fonts/check/ligature_carets

  • ⚠ WARN This font lacks caret positioning values for these ligature glyphs:

    • uni247B
    • uni2498
    • uni248C
    • uni2491
    • uni2479
    • uni247E
    • uni2484
    • uni2472
    • uni2493
    • uni24B3
    • uni24A3
    • uni24AE
    • uni248E
    • uni24AB
    • uni24B2
    • uni2462
    • uni2494
    • uni2481
    • uni24B4
    • uni2465
    • uni2474
    • uni2470
    • uni2488
    • uni246C
    • uni24A8
    • uni2492
    • uni24A1
    • uni24B1
    • uni247D
    • uni2496
    • uni24B0
    • uni247F
    • uni2485
    • uni246B
    • uni2489
    • uni2473
    • uni24A4
    • uni2483
    • uni2480
    • exclamdbl
    • f_thorn
    • uni247A
    • uni249B
    • uni2478
    • uni24A5
    • uni2049
    • uni2497
    • uni2048
    • uni24AC
    • uni24AF
    • uni2471
    • uni24AD
    • uni247C
    • uni24A9
    • uni2475
    • uni2482
    • uni2463
    • ellipsis
    • uni2495
    • uni248F
    • uni24A0
    • uni24A7
    • uni249E
    • uni2477
    • uni2476
    • uni2047
    • uni2469
    • uni246E
    • uni2460
    • uni248B
    • uni2490
    • uni24B5
    • uni2036
    • uni2487
    • uni248A
    • uni249D
    • uni2037
    • uhorn
    • f_eth
    • uniF1BC
    • uni249F
    • uni248D
    • uni2486
    • uni246A
    • uni24A2
    • uni249C
    • uni2467
    • uni2468
    • twodotenleader
    • uni2464
    • uni2466
    • f_nordicthorn
    • uni249A
    • uniF4FF
    • uni24A6
    • uni2499
    • uni246D
    • uni246F
    • uni2461
    • uni24AA

    [code: incomplete-caret-pos-data]

⚠ 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:

    • parenleft + o
    • o + parenright
    • parenright + n
    • n + parenright
    • parenright + m
    • m + parenright
    • parenright + l
    • l + parenright
    • parenright + k
    • k + parenright
    • parenright + j
    • j + parenright
    • parenright + i
    • i + parenright
    • parenright + h
    • h + parenright
    • parenright + g
    • g + parenright
    • parenright + f
    • f + parenright
    • parenright + e
    • e + parenright
    • parenright + d
    • d + parenright
    • parenright + c
    • c + parenright
    • parenright + b
    • b + parenright
    • parenright + a
    • a + parenright
    • parenright + z
    • z + parenright
    • parenright + y
    • y + parenright
    • parenright + x
    • x + parenright
    • parenright + w
    • w + parenright
    • parenright + v
    • v + parenright
    • parenright + u
    • u + parenright
    • parenright + t
    • t + parenright
    • parenright + s
    • s + parenright
    • parenright + r
    • r + parenright
    • parenright + q
    • q + parenright
    • parenright + p
    • p + parenright
    • parenright + nine
    • nine + parenright
    • parenright + eight
    • eight + parenright
    • parenright + seven
    • seven + parenright
    • parenright + six
    • six + parenright
    • parenright + five
    • five + parenright
    • parenright + four
    • four + parenright
    • parenright + three
    • three + parenright
    • parenright + two
    • two + parenright
    • parenright + one
    • one + parenright
    • period + period
    • one + period
    • period + uni20DD
    • two + period
    • f + nordicthorn
    • nordicthorn + eth
    • eth + y
    • y + udieresis
    • udieresis + t
    • t + r
    • r + odieresis
    • odieresis + j
    • j + thorn
    • thorn + nordiceth
    • nordiceth + l
    • l + i
    • i + f
    • slong + udieresis
    • udieresis + odieresis
    • odieresis + adieresis
    • adieresis + j
    • j + s
    • s + p
    • p + b
    • b + i
    • i + k
    • k + h
    • h + l
    • l + slong
    • slong + t
    • uni2035 + uni2035
    • exclam + question
    • question + exclam
    • three + period
    • four + period
    • five + period
    • six + period
    • seven + period
    • eight + period
    • nine + period
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • l + j
    • n + j
    • u + hornnosp

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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.
  • com.google.fonts/check/canonical_filename
  • 🔥 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: Check glyph coverage.
🔥 FAIL: License URL matches License text on name table?
🔥 FAIL: Version format is correct in 'name' table?
  • com.google.fonts/check/name/version_format
  • 🔥 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
  • com.google.fonts/check/font_copyright
  • 🔥 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.
  • com.google.fonts/check/name/subfamilyname
  • 🔥 FAIL SUBFAMILY_NAME for Mac "RegularCondensed" must be "Condensed Regular" [code: bad-familyname]
  • 🔥 FAIL SUBFAMILY_NAME for Win "RegularCondensed" must be "Regular" [code: bad-familyname]
🔥 FAIL: Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
  • com.google.fonts/check/smart_dropout
  • 🔥 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.
  • com.google.fonts/check/name/trailing_spaces
  • 🔥 FAIL Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
  • 🔥 FAIL Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 0.6.17 '
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
🔥 FAIL: Are there unwanted tables?
  • com.google.fonts/check/unwanted_tables
  • 🔥 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.
  • com.google.fonts/check/name/line_breaks
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break.
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break.
🔥 FAIL: Does the font have a DSIG table?
  • com.google.fonts/check/dsig
  • 🔥 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: Checking OS/2 achVendID.
⚠ WARN: Is 'gasp' table set to optimize rendering?
⚠ WARN: Stricter unitsPerEm criteria for Google Fonts.
  • com.google.fonts/check/unitsperem_strict
  • ⚠ 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.
  • 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: aogonek Contours detected: 3 Expected: 2
Glyph name: uni01BB Contours detected: 2 Expected: 1
Glyph name: uni01C2 Contours detected: 3 Expected: 1
Glyph name: uni01E5 Contours detected: 4 Expected: 2
Glyph name: uni01F5 Contours detected: 4 Expected: 3
Glyph name: uni0228 Contours detected: 2 Expected: 1
Glyph name: uni0229 Contours detected: 3 Expected: 2
Glyph name: uni203D Contours detected: 3 Expected: 2
Glyph name: uni03D7 Contours detected: 2 Expected: 1
Glyph name: uniF200 Contours detected: 2 Expected: 14
Glyph name: Ccedillaacute Contours detected: 3 Expected: 2
Glyph name: ccedillaacute Contours detected: 3 Expected: 2
Glyph name: Ecedillabreve Contours detected: 3 Expected: 2
Glyph name: ecedillabreve Contours detected: 4 Expected: 3
Glyph name: uni2158 Contours detected: 3 Expected: 4
Glyph name: uniEFFD Contours detected: 4 Expected: 9 or 7

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

  • com.google.fonts/check/ligature_carets

  • ⚠ WARN This font lacks caret positioning values for these ligature glyphs:

    • uni247B
    • uni2498
    • uni248C
    • uni2491
    • uni2479
    • uni247E
    • uni2484
    • uni2472
    • uni2493
    • uni24B3
    • uni24A3
    • uni24AE
    • uni248E
    • uni24AB
    • uni24B2
    • uni2462
    • uni2494
    • uni2481
    • uni24B4
    • uni2465
    • uni2474
    • uni2470
    • uni2488
    • uni246C
    • uni24A8
    • uni2492
    • uni24A1
    • uni24B1
    • uni247D
    • uni2496
    • uni24B0
    • uni247F
    • uni2485
    • uni246B
    • uni2489
    • uni2473
    • uni24A4
    • uni2483
    • uni2480
    • exclamdbl
    • f_thorn
    • uni247A
    • uni249B
    • uni2478
    • uni24A5
    • uni2049
    • uni2497
    • uni2048
    • uni24AC
    • uni24AF
    • uni2471
    • uni24AD
    • uni247C
    • uni24A9
    • uni2475
    • uni2482
    • uni2463
    • ellipsis
    • uni2495
    • uni248F
    • uni24A0
    • uni24A7
    • uni249E
    • uni2477
    • uni2476
    • uni2047
    • uni2469
    • uni246E
    • uni2460
    • uni248B
    • uni2490
    • uni24B5
    • uni2036
    • uni2487
    • uni248A
    • uni249D
    • uni2037
    • uhorn
    • f_eth
    • uniF1BC
    • uni249F
    • uni248D
    • uni2486
    • uni246A
    • uni24A2
    • uni249C
    • uni2467
    • uni2468
    • twodotenleader
    • uni2464
    • uni2466
    • f_nordicthorn
    • uni249A
    • uniF4FF
    • uni24A6
    • uni2499
    • uni246D
    • uni246F
    • uni2461
    • uni24AA

    [code: incomplete-caret-pos-data]

⚠ 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:

    • parenleft + o
    • o + parenright
    • parenright + n
    • n + parenright
    • parenright + m
    • m + parenright
    • parenright + l
    • l + parenright
    • parenright + k
    • k + parenright
    • parenright + j
    • j + parenright
    • parenright + i
    • i + parenright
    • parenright + h
    • h + parenright
    • parenright + g
    • g + parenright
    • parenright + f
    • f + parenright
    • parenright + e
    • e + parenright
    • parenright + d
    • d + parenright
    • parenright + c
    • c + parenright
    • parenright + b
    • b + parenright
    • parenright + a
    • a + parenright
    • parenright + z
    • z + parenright
    • parenright + y
    • y + parenright
    • parenright + x
    • x + parenright
    • parenright + w
    • w + parenright
    • parenright + v
    • v + parenright
    • parenright + u
    • u + parenright
    • parenright + t
    • t + parenright
    • parenright + s
    • s + parenright
    • parenright + r
    • r + parenright
    • parenright + q
    • q + parenright
    • parenright + p
    • p + parenright
    • parenright + nine
    • nine + parenright
    • parenright + eight
    • eight + parenright
    • parenright + seven
    • seven + parenright
    • parenright + six
    • six + parenright
    • parenright + five
    • five + parenright
    • parenright + four
    • four + parenright
    • parenright + three
    • three + parenright
    • parenright + two
    • two + parenright
    • parenright + one
    • one + parenright
    • period + period
    • one + period
    • period + uni20DD
    • two + period
    • f + nordicthorn
    • nordicthorn + eth
    • eth + y
    • y + udieresis
    • udieresis + t
    • t + r
    • r + odieresis
    • odieresis + j
    • j + thorn
    • thorn + nordiceth
    • nordiceth + l
    • l + i
    • i + f
    • slong + udieresis
    • udieresis + odieresis
    • odieresis + adieresis
    • adieresis + j
    • j + s
    • s + p
    • p + b
    • b + i
    • i + k
    • k + h
    • h + l
    • l + slong
    • slong + t
    • uni2035 + uni2035
    • exclam + question
    • question + exclam
    • three + period
    • four + period
    • five + period
    • six + period
    • seven + period
    • eight + period
    • nine + period
    • D + z
    • z + Z
    • Z + zcaron
    • zcaron + Zcaron
    • I + J
    • L + j
    • j + J
    • N + j
    • d + z
    • z + zcaron
    • i + j
    • l + j
    • n + j
    • u + hornnosp

    [code: lacks-kern-info]

⚠ WARN: Checking Vertical Metric Linegaps.
⚠ 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:
    • ('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:

  • SKIP
  • INFO
  • PASS

Diff images: out.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.