The following links are broken in the DESCRIPTION file: http://www.impallari.com/projects/overview/poetsen (status code: 404) [code: broken-links]

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]

OS/2 VendorID value 'pyrs' 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)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 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: yi, canadian-aboriginal, tifinagh
• U+02D8 BREVE: try adding one of: yi, canadian-aboriginal
• U+02D9 DOT ABOVE: try adding one of: yi, canadian-aboriginal
• U+02DB OGONEK: try adding one of: yi, canadian-aboriginal
• U+02DD DOUBLE ACUTE ACCENT: not included in any glyphset definition
• U+03BC GREEK SMALL LETTER MU: try adding one of: greek, math
• U+1EB8 LATIN CAPITAL LETTER E WITH DOT BELOW: try adding vietnamese
• U+1EB9 LATIN SMALL LETTER E WITH DOT BELOW: try adding vietnamese
• U+1EBC LATIN CAPITAL LETTER E WITH TILDE: try adding vietnamese
• U+1EBD LATIN SMALL LETTER E WITH TILDE: try adding vietnamese
• U+1ECA LATIN CAPITAL LETTER I WITH DOT BELOW: try adding vietnamese
• U+1ECB LATIN SMALL LETTER I WITH DOT BELOW: try adding vietnamese
• U+1ECC LATIN CAPITAL LETTER O WITH DOT BELOW: try adding vietnamese
• U+1ECD LATIN SMALL LETTER O WITH DOT BELOW: try adding vietnamese
• U+1EE4 LATIN CAPITAL LETTER U WITH DOT BELOW: try adding vietnamese
• U+1EE5 LATIN SMALL LETTER U WITH DOT BELOW: try adding vietnamese
• U+2021 DOUBLE DAGGER: try adding adlam
• U+2030 PER MILLE SIGN: try adding adlam
• U+2070 SUPERSCRIPT ZERO: not included in any glyphset definition
• U+2075 SUPERSCRIPT FIVE: not included in any glyphset definition
• U+2076 SUPERSCRIPT SIX: not included in any glyphset definition
• U+2077 SUPERSCRIPT SEVEN: not included in any glyphset definition
• U+2078 SUPERSCRIPT EIGHT: not included in any glyphset definition
• U+2079 SUPERSCRIPT NINE: not included in any glyphset definition
• U+2080 SUBSCRIPT ZERO: not included in any glyphset definition
• U+2081 SUBSCRIPT ONE: not included in any glyphset definition
• U+2082 SUBSCRIPT TWO: not included in any glyphset definition
• U+2083 SUBSCRIPT THREE: not included in any glyphset definition
• U+2084 SUBSCRIPT FOUR: not included in any glyphset definition
• U+2085 SUBSCRIPT FIVE: not included in any glyphset definition
• U+2086 SUBSCRIPT SIX: not included in any glyphset definition
• U+2087 SUBSCRIPT SEVEN: not included in any glyphset definition
• U+2088 SUBSCRIPT EIGHT: not included in any glyphset definition
• U+2089 SUBSCRIPT NINE: not included in any glyphset definition
• U+2120 SERVICE MARK: not included in any glyphset definition
• U+2153 VULGAR FRACTION ONE THIRD: not included in any glyphset definition
• U+2154 VULGAR FRACTION TWO THIRDS: not included in any glyphset definition
• U+215B VULGAR FRACTION ONE EIGHTH: not included in any glyphset definition
• U+215C VULGAR FRACTION THREE EIGHTHS: not included in any glyphset definition
• U+215D VULGAR FRACTION FIVE EIGHTHS: not included in any glyphset definition
• U+215E VULGAR FRACTION SEVEN EIGHTHS: not included in any glyphset definition
• U+2219 BULLET OPERATOR: try adding one of: symbols, yi, tai-tham, math
• U+F6C3 : 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
• U+FB04 LATIN SMALL LIGATURE FFL: 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) 2012, pablo impallari (www.impallari.com|impallari@gmail.com), rodrigo fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with reserved font name poetsen."

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

A few name table entries with ID=10 (NameID.DESCRIPTION) are longer than 200 characters. Please check whether those entries are copyright notices mistakenly stored in the description string entries by a bug in an old FontLab version. If that's the case, then such copyright notices must be removed from these entries. [code: too-long]

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

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

Unmatched family name in font: TTF has "PoetsenOne" while METADATA.pb has "Poetsen One" [code: mismatch]

Unmatched fullname in font: TTF has "PoetsenOne" while METADATA.pb has "Poetsen One". [code: mismatch]

Unmatched fullname in font: TTF has "PoetsenOne" while METADATA.pb has "Poetsen One". [code: mismatch]

Unmatched familyname in font: TTF has familyname = "PoetsenOne" while METADATA.pb has font.name = "Poetsen One". [code: mismatch]

Unmatched familyname in font: TTF has familyname = "PoetsenOne" while METADATA.pb has font.name = "Poetsen One". [code: mismatch]

METADATA.pb font full_name = "Poetsen One" does not match post_script_name = "PoetsenOne-Regular" [code: mismatch]

METADATA.pb font.name field ("Poetsen One") does not match correct font name format ("PoetsenOne"). [code: mismatch]

METADATA.pb font.name field ("Poetsen One") does not match correct font name format ("PoetsenOne"). [code: mismatch]

METADATA.pb font.full_name field ("Poetsen One") does not match correct font name format ("PoetsenOne"). [code: mismatch]

METADATA.pb font.full_name field ("Poetsen One") does not match correct font name format ("PoetsenOne"). [code: mismatch]

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, pablo impallari (www.impallari.com|impallari@gmail.com) and rodrigo fuenzalida (www.rfuenzalida.com), with reserved font name poetsen." [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, Pablo Impallari (www.impallari.com|impallari@gmail.com) and Rodrigo Fuenzalida (www.rfuenzalida.com), with Reserved Font Name Poetsen." [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, Pablo Impallari (www.impallari.com|impallari@gmail.com) and Rodrigo Fuenzalida (www.rfuenzalida.com), with Reserved Font Name Poetsen." [code: bad-notice-format]

METADATA.pb: copyright field ("Copyright (c) 2012, Pablo Impallari (www.impallari.com|impallari@gmail.com) and Rodrigo Fuenzalida (www.rfuenzalida.com), with Reserved Font Name Poetsen.") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]

METADATA.pb: Fullname "Poetsen One" does not match name table entry "PoetsenOne"! [code: fullname-mismatch]

Regular missing from full name [code: lacks-regular]

GDEF table is missing, but it is mandatory to declare it on fonts that provide ligature glyphs because the caret (text cursor) positioning for each ligature must be provided in this table. [code: GDEF-missing]

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

- f + f

- f + b

- b + f

- f + l

- l + f

- f + i

- i + b

- b + l [code: lacks-kern-info]

Name table entry contains "Reserved Font Name": "Copyright (c) 2012, Pablo Impallari (www.impallari.com|impallari@gmail.com) and Rodrigo Fuenzalida (www.rfuenzalida.com), with Reserved Font Name Poetsen."

This is an error except in a few specific rare cases. [code: rfn]

Name table entry contains "Reserved Font Name": "Copyright (c) 2012, Pablo Impallari (www.impallari.com|impallari@gmail.com) and Rodrigo Fuenzalida (www.rfuenzalida.com), with Reserved Font Name Poetsen."

This is an error except in a few specific rare cases. [code: rfn]

"PoetsenOne" is a CamelCased name. To solve this, simply use spaces instead in the font name. [code: camelcase]

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]

OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/home/runner/work/gf-dashboard/gf-dashboard/fonts/ofl/poetsenone/PoetsenOne-Regular.ttf']. [code: missing-os2-fsselection-bit7]

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

Name table record with key = (1, 0, 0, 10) has trailing spaces that must be removed: 'Inspired b[...]of text. ' [code: trailing-space]

Name table record with key = (3, 1, 1033, 10) has trailing spaces that must be removed: 'Inspired b[...]of text. ' [code: trailing-space]

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

- NULL

- acute.cap

- breve.cap

- caron.alt

- caron.cap

- circumflex.cap

- dieresis.cap

- dotaccent.cap

- dotbelow

- grave.cap

- hungarumlaut.cap

- macron.cap

- nonmarkingreturn

- ring.cap

- tilde.cap

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

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

[code: contour-count]

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

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

Width = 429: less

Width = 543: equal

Width = 431: greater

Width = 613: logicalnot

Width = 513: plusminus

Width = 497: multiply

Width = 483: divide

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

lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

dcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

tcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]

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

The following glyphs should not be used in the "kern" table because they are not in the "cmap" table: f_f_b [code: kern-non-character-glyphs]