Please host your font project on a public Git repo (such as GitHub or GitLab) and place a link in the DESCRIPTION.en_us.html file. [code: lacks-git-url]

Please host your font project on a public Git repo (such as GitHub or GitLab) and place a link in the DESCRIPTION.en_us.html file. [code: lacks-git-url]

OS/2 VendorID is 'PfEd', a font editor default. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]

OS/2 VendorID is 'PfEd', a font editor default. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]

Missing required codepoints:

- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x1E82 (LATIN CAPITAL LETTER W WITH ACUTE)


- 0x1E84 (LATIN CAPITAL LETTER W WITH DIAERESIS)


- 0x1E80 (LATIN CAPITAL LETTER W WITH GRAVE)


- 0x1EF2 (LATIN CAPITAL LETTER Y WITH GRAVE)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x1E83 (LATIN SMALL LETTER W WITH ACUTE)


- 0x1E85 (LATIN SMALL LETTER W WITH DIAERESIS)


- 0x1E81 (LATIN SMALL LETTER W WITH GRAVE)


- 0x1EF3 (LATIN SMALL LETTER Y WITH GRAVE)


- 0x2122 (TRADE MARK SIGN)

[code: missing-codepoints]

Missing required codepoints:

- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x1E82 (LATIN CAPITAL LETTER W WITH ACUTE)


- 0x1E84 (LATIN CAPITAL LETTER W WITH DIAERESIS)


- 0x1E80 (LATIN CAPITAL LETTER W WITH GRAVE)


- 0x1EF2 (LATIN CAPITAL LETTER Y WITH GRAVE)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x1E83 (LATIN SMALL LETTER W WITH ACUTE)


- 0x1E85 (LATIN SMALL LETTER W WITH DIAERESIS)


- 0x1E81 (LATIN SMALL LETTER W WITH GRAVE)


- 0x1EF3 (LATIN SMALL LETTER Y WITH GRAVE)


- 0x2122 (TRADE MARK SIGN)

[code: missing-codepoints]

The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.

• U+02C0 MODIFIER LETTER GLOTTAL STOP: not included in any glyphset definition
• U+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh
• U+02C8 MODIFIER LETTER VERTICAL LINE: not included in any glyphset definition
• U+02D8 BREVE: try adding canadian-aboriginal
• U+02D9 DOT ABOVE: try adding canadian-aboriginal
• U+02DB OGONEK: try adding canadian-aboriginal
• U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
• U+0300 COMBINING GRAVE ACCENT: try adding one of: tai-le, cherokee, coptic
• U+0301 COMBINING ACUTE ACCENT: try adding one of: tai-le, tifinagh, cherokee, coptic
• U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, cherokee, coptic
• U+0303 COMBINING TILDE: not included in any glyphset definition
• U+0304 COMBINING MACRON: try adding one of: gothic, tifinagh, cherokee, coptic
• U+0306 COMBINING BREVE: try adding tifinagh
• U+0307 COMBINING DOT ABOVE: try adding one of: coptic, tai-le, canadian-aboriginal, tifinagh, malayalam
• U+0308 COMBINING DIAERESIS: try adding one of: tai-le, gothic, coptic
• U+030A COMBINING RING ABOVE: not included in any glyphset definition
• U+030B COMBINING DOUBLE ACUTE ACCENT: try adding cherokee
• U+030C COMBINING CARON: try adding one of: tai-le, cherokee
• U+0312 COMBINING TURNED COMMA ABOVE: not included in any glyphset definition
• U+0315 COMBINING COMMA ABOVE RIGHT: not included in any glyphset definition
• U+0326 COMBINING COMMA BELOW: not included in any glyphset definition
• U+0327 COMBINING CEDILLA: not included in any glyphset definition
• U+0328 COMBINING OGONEK: not included in any glyphset definition
• U+2000 EN QUAD: not included in any glyphset definition
• U+2001 EM QUAD: not included in any glyphset definition
• U+2003 EM SPACE: not included in any glyphset definition
• U+2004 THREE-PER-EM SPACE: not included in any glyphset definition
• U+2005 FOUR-PER-EM SPACE: not included in any glyphset definition
• U+2006 SIX-PER-EM SPACE: not included in any glyphset definition
• U+2007 FIGURE SPACE: not included in any glyphset definition
• U+2008 PUNCTUATION SPACE: not included in any glyphset definition
• U+200A HAIR SPACE: not included in any glyphset definition
• U+200C ZERO WIDTH NON-JOINER: try adding one of: rejang, avestan, hanunoo, limbu, bengali, javanese, mongolian, tibetan, tagalog, tifinagh, kaithi, sundanese, brahmi, arabic, balinese, gurmukhi, myanmar, devanagari, sinhala, kannada, tagbanwa, tamil, syloti-nagri, batak, chakma, meetei-mayek, thaana, kayah-li, kharoshthi, saurashtra, mandaic, phags-pa, buhid, oriya, gujarati, telugu, thai, lepcha, new-tai-lue, tai-le, tai-tham, khmer, malayalam, buginese, cham, tai-viet
• U+200D ZERO WIDTH JOINER: try adding one of: rejang, avestan, hanunoo, limbu, bengali, javanese, mongolian, tibetan, tagalog, tifinagh, kaithi, sundanese, brahmi, arabic, balinese, gurmukhi, myanmar, devanagari, sinhala, kannada, tagbanwa, tamil, syloti-nagri, batak, chakma, meetei-mayek, thaana, kayah-li, kharoshthi, saurashtra, mandaic, phags-pa, buhid, oriya, gujarati, telugu, thai, lepcha, new-tai-lue, tai-le, tai-tham, malayalam, buginese, cham, tai-viet
• U+200E LEFT-TO-RIGHT MARK: try adding one of: arabic, phags-pa, thaana
• U+200F RIGHT-TO-LEFT MARK: try adding one of: phags-pa, thaana
• U+2010 HYPHEN: try adding one of: coptic, syloti-nagri, kaithi, sundanese, kayah-li, cham, arabic, kharoshthi, lisu
• U+2011 NON-BREAKING HYPHEN: try adding one of: syloti-nagri, arabic
• U+2012 FIGURE DASH: not included in any glyphset definition
• U+2015 HORIZONTAL BAR: not included in any glyphset definition
• U+201B SINGLE HIGH-REVERSED-9 QUOTATION MARK: not included in any glyphset definition
• U+201F DOUBLE HIGH-REVERSED-9 QUOTATION MARK: not included in any glyphset definition
• U+2021 DOUBLE DAGGER: not included in any glyphset definition
• U+202F NARROW NO-BREAK SPACE: try adding mongolian
• U+203E OVERLINE: not included in any glyphset definition
• U+2053 SWUNG DASH: try adding coptic
• U+205F MEDIUM MATHEMATICAL SPACE: not included in any glyphset definition
• U+2060 WORD JOINER: not included in any glyphset definition

Or you can add the above codepoints to one of the subsets supported by the font: menu, latin, latin-ext [code: unreachable-subsetting]

The following codepoints supported by the font are not covered by any subsets defined in the font's metadata file, and will never be served. You can solve this by either manually adding additional subset declarations to METADATA.pb, or by editing the glyphset definitions.

• U+02C0 MODIFIER LETTER GLOTTAL STOP: not included in any glyphset definition
• U+02C7 CARON: try adding one of: tifinagh, canadian-aboriginal
• U+02C8 MODIFIER LETTER VERTICAL LINE: not included in any glyphset definition
• U+02D8 BREVE: try adding canadian-aboriginal
• U+02D9 DOT ABOVE: try adding canadian-aboriginal
• U+02DB OGONEK: try adding canadian-aboriginal
• U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
• U+0300 COMBINING GRAVE ACCENT: try adding one of: coptic, tai-le, cherokee
• U+0301 COMBINING ACUTE ACCENT: try adding one of: tifinagh, coptic, tai-le, cherokee
• U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: tifinagh, coptic, cherokee
• U+0303 COMBINING TILDE: not included in any glyphset definition
• U+0304 COMBINING MACRON: try adding one of: tifinagh, gothic, coptic, cherokee
• U+0306 COMBINING BREVE: try adding tifinagh
• U+0307 COMBINING DOT ABOVE: try adding one of: coptic, tifinagh, malayalam, tai-le, canadian-aboriginal
• U+0308 COMBINING DIAERESIS: try adding one of: gothic, coptic, tai-le
• U+030A COMBINING RING ABOVE: not included in any glyphset definition
• U+030B COMBINING DOUBLE ACUTE ACCENT: try adding cherokee
• U+030C COMBINING CARON: try adding one of: tai-le, cherokee
• U+0312 COMBINING TURNED COMMA ABOVE: not included in any glyphset definition
• U+0315 COMBINING COMMA ABOVE RIGHT: not included in any glyphset definition
• U+0326 COMBINING COMMA BELOW: not included in any glyphset definition
• U+0327 COMBINING CEDILLA: not included in any glyphset definition
• U+0328 COMBINING OGONEK: not included in any glyphset definition
• U+2000 EN QUAD: not included in any glyphset definition
• U+2001 EM QUAD: not included in any glyphset definition
• U+2003 EM SPACE: not included in any glyphset definition
• U+2004 THREE-PER-EM SPACE: not included in any glyphset definition
• U+2005 FOUR-PER-EM SPACE: not included in any glyphset definition
• U+2006 SIX-PER-EM SPACE: not included in any glyphset definition
• U+2007 FIGURE SPACE: not included in any glyphset definition
• U+2008 PUNCTUATION SPACE: not included in any glyphset definition
• U+200A HAIR SPACE: not included in any glyphset definition
• U+200C ZERO WIDTH NON-JOINER: try adding one of: myanmar, sundanese, kaithi, tibetan, rejang, kharoshthi, brahmi, tai-tham, lepcha, gurmukhi, telugu, javanese, malayalam, arabic, chakma, hanunoo, mongolian, thaana, tai-viet, cham, batak, buginese, gujarati, meetei-mayek, saurashtra, buhid, new-tai-lue, balinese, kayah-li, tagbanwa, tifinagh, thai, bengali, phags-pa, khmer, kannada, devanagari, avestan, oriya, tagalog, limbu, tamil, syloti-nagri, tai-le, sinhala, mandaic
• U+200D ZERO WIDTH JOINER: try adding one of: myanmar, sundanese, kaithi, tibetan, rejang, kharoshthi, brahmi, tai-tham, lepcha, gurmukhi, telugu, javanese, malayalam, arabic, chakma, hanunoo, mongolian, thaana, tai-viet, cham, batak, buginese, gujarati, meetei-mayek, saurashtra, buhid, new-tai-lue, balinese, kayah-li, tagbanwa, tifinagh, thai, bengali, phags-pa, kannada, devanagari, avestan, oriya, tagalog, limbu, tamil, syloti-nagri, tai-le, sinhala, mandaic
• U+200E LEFT-TO-RIGHT MARK: try adding one of: arabic, thaana, phags-pa
• U+200F RIGHT-TO-LEFT MARK: try adding one of: phags-pa, thaana
• U+2010 HYPHEN: try adding one of: coptic, sundanese, kayah-li, kaithi, arabic, syloti-nagri, kharoshthi, lisu, cham
• U+2011 NON-BREAKING HYPHEN: try adding one of: arabic, syloti-nagri
• U+2012 FIGURE DASH: not included in any glyphset definition
• U+2015 HORIZONTAL BAR: not included in any glyphset definition
• U+201B SINGLE HIGH-REVERSED-9 QUOTATION MARK: not included in any glyphset definition
• U+201F DOUBLE HIGH-REVERSED-9 QUOTATION MARK: not included in any glyphset definition
• U+2021 DOUBLE DAGGER: not included in any glyphset definition
• U+202F NARROW NO-BREAK SPACE: try adding mongolian
• U+203E OVERLINE: not included in any glyphset definition
• U+2053 SWUNG DASH: try adding coptic
• U+205F MEDIUM MATHEMATICAL SPACE: not included in any glyphset definition
• U+2060 WORD JOINER: not included in any glyphset definition

Or you can add the above codepoints to one of the subsets supported by the font: menu, latin, latin-ext [code: unreachable-subsetting]

First line in license file is:

"copyright (c) 2011, barry schwartz (chemoelectric@chemoelectric.org)"

which does not match the expected format, similar to:

"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]

First line in license file is:

"copyright (c) 2011, barry schwartz (chemoelectric@chemoelectric.org)"

which does not match the expected format, similar to:

"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

For now we're still accepting http URLs, but you should consider using https instead. [code: http]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

For now we're still accepting http URLs, but you should consider using https instead. [code: http]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]

For now we're still accepting http URLs, but you should consider using https instead. [code: http]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]

Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]

Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]

For now we're still accepting http URLs, but you should consider using https instead. [code: http]

The gasp range 0xFFFF value 0x03 should be set to 0x0F. [code: unset-flags]

METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'latin', 'latin-ext'] and expected ['latin', 'latin-ext', 'menu'] [code: not-sorted]

METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'latin', 'latin-ext'] and expected ['latin', 'latin-ext', 'menu'] [code: not-sorted]

METADATA.pb: Copyright notices should match a pattern similar to: "Copyright 2020 The Familyname Project Authors (git url)" But instead we have got: "copyright (c) 2010, barry schwartz (chemoelectric@chemoelectric.org)" [code: bad-notice-format]

METADATA.pb: Copyright notices should match a pattern similar to: "Copyright 2020 The Familyname Project Authors (git url)" But instead we have got: "copyright (c) 2010, barry schwartz (chemoelectric@chemoelectric.org)" [code: bad-notice-format]

Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: bad-notice-format]

Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: bad-notice-format]

Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: bad-notice-format]

Name Table entry: Copyright notices should match a pattern similar to: "Copyright 2019 The Familyname Project Authors (git url)" But instead we have got: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: bad-notice-format]

Font em size (unitsPerEm) is 4096 which may be too large (causing filesize bloat), unless you are sure that the detail level in this font requires that much precision. [code: large-value]

Font em size (unitsPerEm) is 4096 which may be too large (causing filesize bloat), unless you are sure that the detail level in this font requires that much precision. [code: large-value]

Copyright field for this font on METADATA.pb ("Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org)") differs from a copyright notice entry on the name table: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: mismatch]

Copyright field for this font on METADATA.pb ("Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org)") differs from a copyright notice entry on the name table: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: mismatch]

Copyright field for this font on METADATA.pb ("Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org)") differs from a copyright notice entry on the name table: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: mismatch]

Copyright field for this font on METADATA.pb ("Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org)") differs from a copyright notice entry on the name table: "Copyright (c) 2010, Barry Schwartz (chemoelectric@chemoelectric.org) " [code: mismatch]

The following glyphs have components which themselves are component glyphs: * dieresis * uni00B2 * uni00B3 * uni00B9 * onequarter * onehalf * threequarters * Amacron * Emacron * Imacron * iogonek * Omacron * Ohungarumlaut * ohungarumlaut * Umacron * Uhungarumlaut * uhungarumlaut * Ydieresis * hungarumlaut * adieresis.sc * edieresis.sc * idieresis.sc * odieresis.sc * udieresis.sc * ydieresis.sc * ohungarumlaut.sc * uhungarumlaut.sc * Agrave.c2 * Egrave.c2 * Igrave.c2 * Ograve.c2 * Aacute.c2 * Cacute.c2 * Eacute.c2 * Iacute.c2 * Lacute.c2 * Nacute.c2 * Oacute.c2 * Racute.c2 * Sacute.c2 * Uacute.c2 * Yacute.c2 * Zacute.c2 * Ccaron.c2 * Dcaron.c2 * Ecaron.c2 * Ncaron.c2 * Rcaron.c2 * Scaron.c2 * Tcaron.c2 * Zcaron.c2 * Acircumflex.c2 * Ccircumflex.c2 * Ecircumflex.c2 * Gcircumflex.c2 * Hcircumflex.c2 * Icircumflex.c2 * Jcircumflex.c2 * Ocircumflex.c2 * Scircumflex.c2 * Ucircumflex.c2 * Wcircumflex.c2 * Ycircumflex.c2 * Cdotaccent.c2 * Edotaccent.c2 * Gdotaccent.c2 * Zdotaccent.c2 * Aring.c2 * Uring.c2 * Adieresis.c2 * Edieresis.c2 * Idieresis.c2 * Odieresis.c2 * Udieresis.c2 * Ydieresis.c2 * Ohungarumlaut.c2 * Uhungarumlaut.c2 * Amacron.c2 * Emacron.c2 * Imacron.c2 * Omacron.c2 * Umacron.c2 * Abreve.c2 * Ebreve.c2 * Gbreve.c2 * Ibreve.c2 * Obreve.c2 * Ubreve.c2 * Atilde.c2 * Itilde.c2 * Ntilde.c2 * Otilde.c2 * Utilde.c2 * Gcommaaccent.c2 * Kcommaaccent.c2 * Lcommaaccent.c2 * Ncommaaccent.c2 * Rcommaaccent.c2 * Lcaron.c2 * Dcroat.c2 * Ldot.c2 * Ugrave.c2 * uni0218.c2 * uni021A.c2 * L.CAT.c2 * IJ.c2 and i.TRK.sc [code: found-nested-components]

The following glyphs have components which themselves are component glyphs: * seven * eight * uni00B2 * uni00B3 * uni00B9 * onequarter * onehalf * threequarters * Aring * iogonek * Ohungarumlaut * Uring * Uhungarumlaut * Ydieresis * Adieresis.001 * Aring.001 and Edieresis.001 [code: found-nested-components]

This font lacks caret positioning values for these ligature glyphs: - Ldot - Ldot.c2 - f_b - f_f - f_f_b - f_f_h - f_f_hcircumflex - f_f_i - f_f_j - f_f_k - f_f_l - f_f_thorn - f_h - f_hcircumflex - f_i - f_j - f_k - f_l - f_thorn - ldot.sc - longs_h - longs_i - longs_j - longs_k - longs_l - longs_longs - longs_longs_b - longs_longs_h - longs_longs_i - longs_longs_j - longs_longs_k - longs_longs_l - longs_longs_thorn - longs_thorn

[code: incomplete-caret-pos-data]

This font lacks caret positioning values for these ligature glyphs: - Ldot - f_b - f_f - f_f_b - f_f_h - f_f_hcircumflex - f_f_i - f_f_j - f_f_k.001 - f_f_l - f_f_thorn - f_h - f_hcircumflex - f_i - f_j - f_k - f_k.001 - f_l - f_thorn - longs_b - longs_h - longs_i - longs_j - longs_k - longs_k.001 - longs_l - longs_longs - longs_longs_b - longs_longs_h - longs_longs_i - longs_longs_j - longs_longs_k - longs_longs_k.001 - longs_longs_l - longs_longs_thorn - longs_thorn

[code: incomplete-caret-pos-data]

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

- f + f

- f + hcircumflex

- hcircumflex + f

- f + thorn

- thorn + f

- f + k

- k + f

- f + h

- h + f

- f + b

- b + f

- f + j

- j + f

- f + l

- l + f

- f + i

- i + hcircumflex

- hcircumflex + b

- b + k

- k + j

- j + thorn

- thorn + h

- l + i

- longs + longs

- longs + thorn

- thorn + longs

- longs + k

- k + longs

- longs + h

- h + longs

- longs + b

- b + longs

- longs + j

- j + longs

- longs + l

- l + longs

- longs + i

- i + b

- b + thorn

- thorn + j

- j + h

- h + k

- L.CAT + periodcentered

- L.CAT.c2 + periodcentered.c2

- l.CAT.sc + periodcentered.sc [code: lacks-kern-info]

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

- f + f

- f + k.001

- k.001 + f

- f + hcircumflex

- hcircumflex + f

- f + thorn

- thorn + f

- f + k

- k + f

- f + h

- h + f

- f + b

- b + f

- f + j

- j + f

- f + l

- l + f

- f + i

- i + h

- h + thorn

- thorn + b

- b + hcircumflex

- hcircumflex + j

- j + k

- k + k.001

- l + i

- longs + longs

- longs + k.001

- k.001 + longs

- longs + thorn

- thorn + longs

- longs + k

- k + longs

- longs + h

- h + longs

- longs + b

- b + longs

- longs + j

- j + longs

- longs + l

- l + longs

- longs + i

- i + k.001

- k.001 + b

- b + k

- k + j

- j + thorn

- thorn + h

- L.CAT + periodcentered [code: lacks-kern-info]

Name entry COPYRIGHT_NOTICE on platform MACINTOSH contains a line-break. [code: line-break]

Name entry COPYRIGHT_NOTICE on platform WINDOWS contains a line-break. [code: line-break]

Name entry COPYRIGHT_NOTICE on platform MACINTOSH contains a line-break. [code: line-break]

Name entry COPYRIGHT_NOTICE on platform WINDOWS contains a line-break. [code: line-break]

Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

The DESCRIPTION.en_us.html file in this family has not changed in comparison to the latest font release on the google/fonts github repo. Please consider mentioning note-worthy improvements made to the family recently. [code: description-not-updated]

The DESCRIPTION.en_us.html file in this family has not changed in comparison to the latest font release on the google/fonts github repo. Please consider mentioning note-worthy improvements made to the family recently. [code: description-not-updated]

This font file does not have a 'meta' table. [code: lacks-meta-table]

This font file does not have a 'meta' table. [code: lacks-meta-table]

This font file contains the following pre-production tables: FFTM [code: has-debugging-tables]

This font file contains the following pre-production tables: FFTM [code: has-debugging-tables]

usWinDescent is not the same across the family: Linden Hill: 1081 Linden Hill Italic: 1888 [code: usWinDescent-mismatch]

Name table record with key = (1, 0, 0, 0) has trailing spaces that must be removed: 'Copyright [...]tric.org) ' [code: trailing-space]

Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 1.202 ' [code: trailing-space]

Name table record with key = (3, 1, 1033, 0) has trailing spaces that must be removed: 'Copyright [...]tric.org) ' [code: trailing-space]

Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 1.202 ' [code: trailing-space]

Name table record with key = (1, 0, 0, 0) has trailing spaces that must be removed: 'Copyright [...]tric.org) ' [code: trailing-space]

Name table record with key = (1, 0, 0, 5) has trailing spaces that must be removed: 'Version 1.201 ' [code: trailing-space]

Name table record with key = (3, 1, 1033, 0) has trailing spaces that must be removed: 'Copyright [...]tric.org) ' [code: trailing-space]

Name table record with key = (3, 1, 1033, 5) has trailing spaces that must be removed: 'Version 1.201 ' [code: trailing-space]

OS/2.usWinDescent value should be equal or greater than 1888, but got 1081 instead [code: descent]

ots-sanitize passed this file, however warnings were printed:

WARNING: gasp: Changed the version number to 1 [code: ots-sanitize-warn]

The following unwanted font tables were found:

• FFTM - Table contains redundant FontForge timestamp info

They can be removed with the 'fix-unwanted-tables' script provided by gftools. [code: unwanted-tables]

The following unwanted font tables were found:

• FFTM - Table contains redundant FontForge timestamp info

They can be removed with the 'fix-unwanted-tables' script provided by gftools. [code: unwanted-tables]

The following glyphs could not be reached by codepoint or substitution rules:

- nonmarkingreturn

- uni0308.narrow

[code: unreachable-glyphs]

The following glyphs could not be reached by codepoint or substitution rules:

- nonmarkingreturn

[code: unreachable-glyphs]

The following glyphs have no contours even though they were expected to have some:

- Glyph name: uni02C8	Expected: 1

- Glyph name: uni02C8	Expected: 1

[code: no-contour]

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: uni00AD	Contours detected: 1	Expected: 0

- Glyph name: percent	Contours detected: 4	Expected: 5

- Glyph name: uni00AD	Contours detected: 1	Expected: 0

[code: contour-count]

The following glyphs have no contours even though they were expected to have some:

- Glyph name: uni02C8	Expected: 1

- Glyph name: uni02C8	Expected: 1

[code: no-contour]

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: Q	Contours detected: 1	Expected: 2

- Glyph name: uni00AD	Contours detected: 1	Expected: 0

- Glyph name: Q	Contours detected: 1	Expected: 2

- Glyph name: percent	Contours detected: 4	Expected: 5

- Glyph name: uni00AD	Contours detected: 1	Expected: 0

[code: contour-count]

This font has a 'Soft Hyphen' character. [code: softhyphen]

This font has a 'Soft Hyphen' character. [code: softhyphen]

The most common width is 3117 among a set of 2 math glyphs. The following math glyphs have a different width, though:

Width = 3125: plus

Width = 3211: equal

Width = 2949: logicalnot

Width = 2969: plusminus

Width = 2412: multiply

Width = 2965: divide

Width = 3047: minus [code: width-outliers]

The most common width is 3117 among a set of 2 math glyphs. The following math glyphs have a different width, though:

Width = 3125: plus

Width = 3211: equal

Width = 2949: logicalnot

Width = 2969: plusminus

Width = 2412: multiply

Width = 2965: divide

Width = 3047: minus [code: width-outliers]

Version info differs among font files of the same font project. These were the version values found:

• /Users/simon/others-repos/fonts/ofl/lindenhill/LindenHill-Regular.ttf: 1.201995849609375
• /Users/simon/others-repos/fonts/ofl/lindenhill/LindenHill-Italic.ttf: 1.2010040283203125 [code: mismatch]

OS/2 xAvgCharWidth is 2086 but it should be 2009 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]

OS/2 xAvgCharWidth is 1936 but it should be 2074 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]

hhea.caretSlopeRise and hhea.caretSlopeRun do not match with post.italicAngle. Got: caretSlopeRise 100 and caretSlopeRun 10 Expected: caretSlopeRise 4096 and caretSlopeRun 402 [code: caretslope-mismatch]

This font has a digital signature (DSIG table) which is only required - even if only a placeholder - on old programs like MS Office 2013 in order to work properly. The current recommendation is to completely remove the DSIG table. [code: found-DSIG]

This font has a digital signature (DSIG table) which is only required - even if only a placeholder - on old programs like MS Office 2013 in order to work properly. The current recommendation is to completely remove the DSIG table. [code: found-DSIG]

The following mark characters could be in the GDEF mark glyph class: acutecomb (U+0301), gravecomb (U+0300), tildecomb (U+0303), uni0302 (U+0302), uni0304 (U+0304), uni0306 (U+0306), uni0307 (U+0307), uni0308 (U+0308), uni030A (U+030A), uni030B (U+030B), uni030C (U+030C), uni0312 (U+0312), uni0315 (U+0315), uni0326 (U+0326), uni0327 (U+0327) and uni0328 (U+0328) [code: mark-chars]

The following mark characters could be in the GDEF mark glyph class: acutecomb (U+0301), gravecomb (U+0300), tildecomb (U+0303), uni0302 (U+0302), uni0304 (U+0304), uni0306 (U+0306), uni0307 (U+0307), uni0308 (U+0308), uni030A (U+030A), uni030B (U+030B), uni030C (U+030C), uni0312 (U+0312), uni0315 (U+0315), uni0326 (U+0326), uni0327 (U+0327) and uni0328 (U+0328) [code: mark-chars]

The following glyphs have coordinates which are out of bounds: * ('ampersand', 1558, -121) * ('m.sc', 1200, -94) * ('M.c2', 1200, -94) and ('bullet.001', 1911, -152)

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. [code: points-out-of-bounds]

The following glyphs have coordinates which are out of bounds: * ('M', 1537, -92) * ('X', 2218, -109) * ('X', 218, -103) * ('w', 1439, -144) * ('wcircumflex', 1439, -144) * ('z.001', 1962, -684) * ('zacute.001', 1962, -684) * ('zdotaccent.001', 1962, -684) * ('zcaron.001', 1962, -684) * ('M.001', 1533, -92) * ('bullet.003', 1202, -1063) and ('bullet.001', 1911, -152)

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. [code: points-out-of-bounds]

The dot of soft dotted characters used in orthographies must disappear in the following strings: i̊ i̋ j̀ j́ j̃ j̄ j̈ į̀ į́ į̂ į̃ į̄ į̌

The dot of soft dotted characters should disappear in other cases, for example: i̇ ǐ i̒ i̦̇ i̦̊ i̦̋ ǐ̦ i̦̒ i̧̇ i̧̊ i̧̋ ǐ̧ i̧̒ j̆ j̇ j̊ j̋ ǰ j̒ j̦̀

Your font does not cover the following languages that require the soft-dotted feature: Basaa (Latn, 332,940 speakers), Igbo (Latn, 27,823,640 speakers), Belarusian (Cyrl, 10,064,517 speakers), Dutch (Latn, 31,709,104 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Aghem (Latn, 38,843 speakers), Navajo (Latn, 166,319 speakers), Lithuanian (Latn, 2,357,094 speakers). [code: soft-dotted]

The dot of soft dotted characters used in orthographies must disappear in the following strings: i̊ i̋ j̀ j́ j̃ j̄ j̈ į̀ į́ į̂ į̃ į̄ į̌

The dot of soft dotted characters should disappear in other cases, for example: i̇ ǐ i̒ i̦̇ i̦̊ i̦̋ ǐ̦ i̦̒ i̧̇ i̧̊ i̧̋ ǐ̧ i̧̒ j̆ j̇ j̊ j̋ ǰ j̒ j̦̀

Your font does not cover the following languages that require the soft-dotted feature: Basaa (Latn, 332,940 speakers), Igbo (Latn, 27,823,640 speakers), Belarusian (Cyrl, 10,064,517 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Dutch (Latn, 31,709,104 speakers), Navajo (Latn, 166,319 speakers), Lithuanian (Latn, 2,357,094 speakers), Aghem (Latn, 38,843 speakers). [code: soft-dotted]