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]

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]

The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

OS/2 VendorID value 'newt' is not yet recognized. 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: unknown]

OS/2 VendorID value 'newt' is not yet recognized. 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: unknown]

OS/2 VendorID value 'newt' is not yet recognized. 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: unknown]

Missing required codepoints:

- 0x0308 (COMBINING DIAERESIS)


- 0x0300 (COMBINING GRAVE ACCENT)


- 0x0301 (COMBINING ACUTE ACCENT)


- 0x030B (COMBINING DOUBLE ACUTE ACCENT)


- 0x0304 (COMBINING MACRON)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x00B7 (MIDDLE DOT)


- 0x0307 (COMBINING DOT ABOVE)


- 0x0302 (COMBINING CIRCUMFLEX ACCENT)


- 0x030C (COMBINING CARON)


- 0x0306 (COMBINING BREVE)


- 0x030A (COMBINING RING ABOVE)


- 0x0303 (COMBINING TILDE)


- 0x0312 (COMBINING TURNED COMMA ABOVE)


- 0x0326 (COMBINING COMMA BELOW)


- 0x0327 (COMBINING CEDILLA)


- 0x0328 (COMBINING OGONEK)

[code: missing-codepoints]

Missing required codepoints:

- 0x0308 (COMBINING DIAERESIS)


- 0x0300 (COMBINING GRAVE ACCENT)


- 0x0301 (COMBINING ACUTE ACCENT)


- 0x030B (COMBINING DOUBLE ACUTE ACCENT)


- 0x0304 (COMBINING MACRON)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x00B7 (MIDDLE DOT)


- 0x0307 (COMBINING DOT ABOVE)


- 0x0302 (COMBINING CIRCUMFLEX ACCENT)


- 0x030C (COMBINING CARON)


- 0x0306 (COMBINING BREVE)


- 0x030A (COMBINING RING ABOVE)


- 0x0303 (COMBINING TILDE)


- 0x0312 (COMBINING TURNED COMMA ABOVE)


- 0x0326 (COMBINING COMMA BELOW)


- 0x0327 (COMBINING CEDILLA)


- 0x0328 (COMBINING OGONEK)

[code: missing-codepoints]

Missing required codepoints:

- 0x0308 (COMBINING DIAERESIS)


- 0x0300 (COMBINING GRAVE ACCENT)


- 0x0301 (COMBINING ACUTE ACCENT)


- 0x030B (COMBINING DOUBLE ACUTE ACCENT)


- 0x0304 (COMBINING MACRON)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x00B7 (MIDDLE DOT)


- 0x0307 (COMBINING DOT ABOVE)


- 0x0302 (COMBINING CIRCUMFLEX ACCENT)


- 0x030C (COMBINING CARON)


- 0x0306 (COMBINING BREVE)


- 0x030A (COMBINING RING ABOVE)


- 0x0303 (COMBINING TILDE)


- 0x0312 (COMBINING TURNED COMMA ABOVE)


- 0x0326 (COMBINING COMMA BELOW)


- 0x0327 (COMBINING CEDILLA)


- 0x0328 (COMBINING OGONEK)

[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+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh
• U+02C9 MODIFIER LETTER MACRON: 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+030F COMBINING DOUBLE GRAVE ACCENT: not included in any glyphset definition
• U+0311 COMBINING INVERTED BREVE: try adding coptic
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+2021 DOUBLE DAGGER: not included in any glyphset definition
• U+2030 PER MILLE SIGN: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+221E INFINITY: not included in any glyphset definition
• U+222B INTEGRAL: not included in any glyphset definition
• U+2248 ALMOST EQUAL TO: not included in any glyphset definition
• U+2260 NOT EQUAL TO: not included in any glyphset definition
• U+2264 LESS-THAN OR EQUAL TO: not included in any glyphset definition
• U+2265 GREATER-THAN OR EQUAL TO: not included in any glyphset definition
• U+25CA LOZENGE: not included in any glyphset definition
• U+FB00 LATIN SMALL LIGATURE FF: not included in any glyphset definition
• U+FB01 LATIN SMALL LIGATURE FI: not included in any glyphset definition
• U+FB02 LATIN SMALL LIGATURE FL: not included in any glyphset definition
• U+FB03 LATIN SMALL LIGATURE FFI: not included in any glyphset definition

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu [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+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh
• 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+030F COMBINING DOUBLE GRAVE ACCENT: not included in any glyphset definition
• U+0311 COMBINING INVERTED BREVE: try adding coptic
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+2021 DOUBLE DAGGER: not included in any glyphset definition
• U+2030 PER MILLE SIGN: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+221E INFINITY: not included in any glyphset definition
• U+222B INTEGRAL: not included in any glyphset definition
• U+2248 ALMOST EQUAL TO: not included in any glyphset definition
• U+2260 NOT EQUAL TO: not included in any glyphset definition
• U+2264 LESS-THAN OR EQUAL TO: not included in any glyphset definition
• U+2265 GREATER-THAN OR EQUAL TO: not included in any glyphset definition
• U+25CA LOZENGE: not included in any glyphset definition
• U+FB00 LATIN SMALL LIGATURE FF: not included in any glyphset definition
• U+FB01 LATIN SMALL LIGATURE FI: not included in any glyphset definition
• U+FB02 LATIN SMALL LIGATURE FL: not included in any glyphset definition
• U+FB03 LATIN SMALL LIGATURE FFI: not included in any glyphset definition

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu [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+02C7 CARON: try adding one of: canadian-aboriginal, tifinagh
• 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+030F COMBINING DOUBLE GRAVE ACCENT: not included in any glyphset definition
• U+0311 COMBINING INVERTED BREVE: try adding coptic
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+2021 DOUBLE DAGGER: not included in any glyphset definition
• U+2030 PER MILLE SIGN: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+221E INFINITY: not included in any glyphset definition
• U+222B INTEGRAL: not included in any glyphset definition
• U+2248 ALMOST EQUAL TO: not included in any glyphset definition
• U+2260 NOT EQUAL TO: not included in any glyphset definition
• U+2264 LESS-THAN OR EQUAL TO: not included in any glyphset definition
• U+2265 GREATER-THAN OR EQUAL TO: not included in any glyphset definition
• U+25CA LOZENGE: not included in any glyphset definition
• U+FB00 LATIN SMALL LIGATURE FF: not included in any glyphset definition
• U+FB01 LATIN SMALL LIGATURE FI: not included in any glyphset definition
• U+FB02 LATIN SMALL LIGATURE FL: not included in any glyphset definition
• U+FB03 LATIN SMALL LIGATURE FFI: not included in any glyphset definition

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

First line in license file is:

"copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with reserved font name 'benchnine'."

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) 2012, vernon adams (vern@newtypography.co.uk), with reserved font name 'benchnine'."

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) 2012, vernon adams (vern@newtypography.co.uk), with reserved font name 'benchnine'."

which does not match the expected format, similar to:

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

The OFL.txt body text is incorrect. Please use https://github.com/googlefonts/Unified-Font-Repository/blob/main/OFL.txt as a template. You should only modify the first line. [code: incorrect-ofl-body-text]

The OFL.txt body text is incorrect. Please use https://github.com/googlefonts/Unified-Font-Repository/blob/main/OFL.txt as a template. You should only modify the first line. [code: incorrect-ofl-body-text]

The OFL.txt body text is incorrect. Please use https://github.com/googlefonts/Unified-Font-Repository/blob/main/OFL.txt as a template. You should only modify the first line. [code: incorrect-ofl-body-text]

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=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]

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 NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g"" [code: bad-version-strings]

The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g"" [code: bad-version-strings]

The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g"" [code: bad-version-strings]

The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g"" [code: bad-version-strings]

The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g"" [code: bad-version-strings]

The NameID.VERSION_STRING (nameID=5) value must follow the pattern "Version X.Y" with X.Y greater than or equal to 1.000. Current version string is: "Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g"" [code: bad-version-strings]

ttfautohint used in font = 0.92.18-e454-dirty; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]

ttfautohint used in font = 0.92.18-e454-dirty; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]

ttfautohint used in font = 0.92.18-e454-dirty; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]

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) 2012, vernon adams (vern@newtypography.co.uk), with reserved font name 'benchnine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with reserved font name 'benchnine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with reserved font name 'benchnine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'" [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) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'" [code: bad-notice-format]

METADATA.pb: copyright field ("Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]

METADATA.pb: copyright field ("Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]

METADATA.pb: copyright field ("Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine'") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]

The following glyphs have components which themselves are component glyphs: * uni01C4 * uni01C5 and uni01C6 [code: found-nested-components]

The following glyphs have components which themselves are component glyphs: * uni01C4 * uni01C5 and uni01C6 [code: found-nested-components]

The following glyphs have components which themselves are component glyphs: * uni01C4 * uni01C5 and uni01C6 [code: found-nested-components]

This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]

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

- f + f

- f + i

- i + l

- l + i

- i + f [code: lacks-kern-info]

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]

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

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'BenchNine'. Please use an unicode string instead. [code: escaped-strings]

Found escaped chars at 'Copyright (c) 2012, vernon adams (vern@newtypography.co.uk), with Reserved Font Name 'BenchNine''. Please use an unicode string instead. [code: escaped-strings]

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]

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]

OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/benchnine/BenchNine-Bold.ttf']. [code: missing-os2-fsselection-bit7]

OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/benchnine/BenchNine-Bold.ttf']. [code: missing-os2-fsselection-bit7]

OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/benchnine/BenchNine-Bold.ttf']. [code: missing-os2-fsselection-bit7]

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

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

OS/2.usWinAscent value should be equal or greater than 2029, but got 2020 instead [code: ascent]

OS/2.usWinAscent value should be equal or greater than 2029, but got 2020 instead [code: ascent]

OS/2.usWinAscent value should be equal or greater than 2029, but got 2020 instead [code: ascent]

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

- glyph00001

- glyph00002

[code: unreachable-glyphs]

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

- glyph00001

- glyph00002

[code: unreachable-glyphs]

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

- glyph00001

- glyph00002

[code: unreachable-glyphs]

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: dollar	Contours detected: 2	Expected: 1, 3 or 5

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

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

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

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

- Glyph name: uni01F5	Contours detected: 4	Expected: 3

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

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: dollar	Contours detected: 2	Expected: 1, 3 or 5

- Glyph name: eogonek	Contours detected: 3	Expected: 2

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

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

[code: contour-count]

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

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

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

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

- Glyph name: uni01F5	Contours detected: 4	Expected: 3

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

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

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

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

[code: contour-count]

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: dollar	Contours detected: 2	Expected: 1, 3 or 5

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

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

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

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

- Glyph name: uni01F5	Contours detected: 4	Expected: 3

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

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: dollar	Contours detected: 2	Expected: 1, 3 or 5

- Glyph name: eogonek	Contours detected: 3	Expected: 2

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

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

[code: contour-count]

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

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

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

The following glyphs had components with scaling or rotation or inverted outline direction:

• dollar (component bar)
• exclamdown (component exclam)
• questiondown (component question)
• uni0123 (component comma) [code: transformed-components]

The following glyphs had components with scaling or rotation or inverted outline direction:

• exclamdown (component exclam)
• questiondown (component question)
• uni0123 (component comma) [code: transformed-components]

The following glyphs had components with scaling or rotation or inverted outline direction:

• dollar (component bar)
• exclamdown (component exclam)
• questiondown (component question)
• uni0123 (component comma) [code: transformed-components]

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

Width = 801: plusminus, plus, multiply

Width = 520: equal

Width = 1012: logicalnot

Width = 796: divide

Width = 875: minus

Width = 816: approxequal

Width = 643: notequal [code: width-outliers]

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

Width = 1073: less, greater

Width = 560: equal

Width = 1106: logicalnot

Width = 802: plusminus

Width = 867: divide

Width = 1024: minus

Width = 949: approxequal

Width = 693: notequal

Width = 582: lessequal

Width = 581: greaterequal [code: width-outliers]

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

Width = 801: plusminus, plus, multiply

Width = 469: equal

Width = 895: logicalnot

Width = 310: divide

Width = 689: minus

Width = 1345: approxequal

Width = 699: notequal [code: width-outliers]

dcaron uses component comma. [code: bad-mark]

Lcaron uses component comma. [code: bad-mark]

lcaron uses component comma. [code: bad-mark]

tcaron uses component comma. [code: bad-mark]

Failed with AttributeError: 'table_O_S_2f_2' object has no attribute 'sxHeight'

dcaron uses component comma. [code: bad-mark]

Lcaron uses component comma. [code: bad-mark]

lcaron uses component comma. [code: bad-mark]

tcaron uses component comma. [code: bad-mark]

name version string for platform 1, encoding 0 ("Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g""), could not be parsed. [code: parse]

name version string for platform 3, encoding 1 ("Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g""), could not be parsed. [code: parse]

name version string for platform 1, encoding 0 ("Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g""), could not be parsed. [code: parse]

name version string for platform 3, encoding 1 ("Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g""), could not be parsed. [code: parse]

name version string for platform 1, encoding 0 ("Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g""), could not be parsed. [code: parse]

name version string for platform 3, encoding 1 ("Version 1 ; ttfautohint (v0.92.18-e454-dirty) -l 8 -r 50 -G 200 -x 0 -w "g""), could not be parsed. [code: parse]

PANOSE proportion is not the same across 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. [code: inconsistency]

PANOSE family type is not the same across 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. [code: inconsistency]

Post table format 3 use has niche use case problems.Please review the check rationale for additional details. [code: post-table-version]

Post table format 3 use has niche use case problems.Please review the check rationale for additional details. [code: post-table-version]

Post table format 3 use has niche use case problems.Please review the check rationale for additional details. [code: post-table-version]

The following mark characters could be in the GDEF mark glyph class: uni030F (U+030F) and uni0311 (U+0311) [code: mark-chars]

The following mark characters could be in the GDEF mark glyph class: uni030F (U+030F) and uni0311 (U+0311) [code: mark-chars]

The following mark characters could be in the GDEF mark glyph class: uni030F (U+030F) and uni0311 (U+0311) [code: mark-chars]

The following glyphs have coordinates which are out of bounds: * ('bracketleft', 116, -125) * ('bracketleft', 116, 1466) * ('bracketright', 468, 1433) and ('bracketright', 468, -128)

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: * ('guillemotleft', 383, 233)

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: j̑

The dot of soft dotted characters should disappear in other cases, for example: j̏ į̏ į̑

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

The dot of soft dotted characters used in orthographies must disappear in the following strings: j̑

The dot of soft dotted characters should disappear in other cases, for example: j̏ į̏ į̑

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

The dot of soft dotted characters used in orthographies must disappear in the following strings: j̑

The dot of soft dotted characters should disappear in other cases, for example: j̏ į̏ į̑

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