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]

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]

Missing required codepoints:

- 0x0308 (COMBINING DIAERESIS)


- 0x0300 (COMBINING GRAVE ACCENT)


- 0x0301 (COMBINING ACUTE ACCENT)


- 0x030B (COMBINING DOUBLE ACUTE ACCENT)


- 0x0304 (COMBINING MACRON)


- 0x010A (LATIN CAPITAL LETTER C WITH DOT ABOVE)


- 0x0120 (LATIN CAPITAL LETTER G WITH DOT ABOVE)


- 0x0126 (LATIN CAPITAL LETTER H WITH STROKE)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x016C (LATIN CAPITAL LETTER U WITH BREVE)


- 0x010B (LATIN SMALL LETTER C WITH DOT ABOVE)


- 0x0121 (LATIN SMALL LETTER G WITH DOT ABOVE)


- 0x0127 (LATIN SMALL LETTER H WITH STROKE)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x016D (LATIN SMALL LETTER U WITH BREVE)


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


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


- 0x010A (LATIN CAPITAL LETTER C WITH DOT ABOVE)


- 0x0120 (LATIN CAPITAL LETTER G WITH DOT ABOVE)


- 0x0126 (LATIN CAPITAL LETTER H WITH STROKE)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x016C (LATIN CAPITAL LETTER U WITH BREVE)


- 0x010B (LATIN SMALL LETTER C WITH DOT ABOVE)


- 0x0121 (LATIN SMALL LETTER G WITH DOT ABOVE)


- 0x0127 (LATIN SMALL LETTER H WITH STROKE)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x016D (LATIN SMALL LETTER U WITH BREVE)


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


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


- 0x010A (LATIN CAPITAL LETTER C WITH DOT ABOVE)


- 0x0120 (LATIN CAPITAL LETTER G WITH DOT ABOVE)


- 0x0126 (LATIN CAPITAL LETTER H WITH STROKE)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x016C (LATIN CAPITAL LETTER U WITH BREVE)


- 0x010B (LATIN SMALL LETTER C WITH DOT ABOVE)


- 0x0121 (LATIN SMALL LETTER G WITH DOT ABOVE)


- 0x0127 (LATIN SMALL LETTER H WITH STROKE)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x016D (LATIN SMALL LETTER U WITH BREVE)


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


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


- 0x010A (LATIN CAPITAL LETTER C WITH DOT ABOVE)


- 0x0120 (LATIN CAPITAL LETTER G WITH DOT ABOVE)


- 0x0126 (LATIN CAPITAL LETTER H WITH STROKE)


- 0x014A (LATIN CAPITAL LETTER ENG)


- 0x1E9E (LATIN CAPITAL LETTER SHARP S)


- 0x016C (LATIN CAPITAL LETTER U WITH BREVE)


- 0x010B (LATIN SMALL LETTER C WITH DOT ABOVE)


- 0x0121 (LATIN SMALL LETTER G WITH DOT ABOVE)


- 0x0127 (LATIN SMALL LETTER H WITH STROKE)


- 0x014B (LATIN SMALL LETTER ENG)


- 0x016D (LATIN SMALL LETTER U WITH BREVE)


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


- 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+0326 COMBINING COMMA BELOW: not included in any glyphset definition
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+03A9 GREEK CAPITAL LETTER OMEGA: try adding greek
• U+03BC GREEK SMALL LETTER MU: try adding greek
• U+03C0 GREEK SMALL LETTER PI: 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+2126 OHM SIGN: not included in any glyphset definition
• U+212E ESTIMATED SYMBOL: not included in any glyphset definition
• U+2202 PARTIAL DIFFERENTIAL: not included in any glyphset definition
• U+2206 INCREMENT: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+2211 N-ARY SUMMATION: not included in any glyphset definition
• U+2219 BULLET OPERATOR: try adding tai-tham
• U+221A SQUARE ROOT: 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+E000 : 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

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: tifinagh, canadian-aboriginal
• 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+0326 COMBINING COMMA BELOW: not included in any glyphset definition
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+03A9 GREEK CAPITAL LETTER OMEGA: try adding greek
• U+03BC GREEK SMALL LETTER MU: try adding greek
• U+03C0 GREEK SMALL LETTER PI: 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+2126 OHM SIGN: not included in any glyphset definition
• U+212E ESTIMATED SYMBOL: not included in any glyphset definition
• U+2202 PARTIAL DIFFERENTIAL: not included in any glyphset definition
• U+2206 INCREMENT: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+2211 N-ARY SUMMATION: not included in any glyphset definition
• U+2219 BULLET OPERATOR: try adding tai-tham
• U+221A SQUARE ROOT: 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+E000 : 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

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: tifinagh, canadian-aboriginal
• 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+0326 COMBINING COMMA BELOW: not included in any glyphset definition
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+03A9 GREEK CAPITAL LETTER OMEGA: try adding greek
• U+03BC GREEK SMALL LETTER MU: try adding greek
• U+03C0 GREEK SMALL LETTER PI: 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+2126 OHM SIGN: not included in any glyphset definition
• U+212E ESTIMATED SYMBOL: not included in any glyphset definition
• U+2202 PARTIAL DIFFERENTIAL: not included in any glyphset definition
• U+2206 INCREMENT: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+2211 N-ARY SUMMATION: not included in any glyphset definition
• U+2219 BULLET OPERATOR: try adding tai-tham
• U+221A SQUARE ROOT: 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+E000 : 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

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+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+0326 COMBINING COMMA BELOW: not included in any glyphset definition
• U+0394 GREEK CAPITAL LETTER DELTA: try adding greek
• U+03A9 GREEK CAPITAL LETTER OMEGA: try adding greek
• U+03BC GREEK SMALL LETTER MU: try adding greek
• U+03C0 GREEK SMALL LETTER PI: 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+2126 OHM SIGN: not included in any glyphset definition
• U+212E ESTIMATED SYMBOL: not included in any glyphset definition
• U+2202 PARTIAL DIFFERENTIAL: not included in any glyphset definition
• U+2206 INCREMENT: not included in any glyphset definition
• U+220F N-ARY PRODUCT: not included in any glyphset definition
• U+2211 N-ARY SUMMATION: not included in any glyphset definition
• U+2219 BULLET OPERATOR: try adding tai-tham
• U+221A SQUARE ROOT: 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+E000 : 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

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 2016 the unna project authors (omnibus.type@gmail.com)"

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 2016 the unna project authors (omnibus.type@gmail.com)"

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 2016 the unna project authors (omnibus.type@gmail.com)"

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 2016 the unna project authors (omnibus.type@gmail.com)"

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

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]

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

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

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

ttfautohint used in font = 1.5; 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 2016 the unna project authors (omnibus.type@gmail.com)" [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 2016 the unna project authors (omnibus.type@gmail.com)" [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 2016 the unna project authors (omnibus.type@gmail.com)" [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 2016 the unna project authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [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 2016 The Unna Project Authors (omnibus.type@gmail.com)" [code: bad-notice-format]

The following glyphs have components which themselves are component glyphs: * Adieresis [code: found-nested-components]

The following glyphs have components which themselves are component glyphs: * Adieresis [code: found-nested-components]

The following glyphs have components which themselves are component glyphs: * Adieresis [code: found-nested-components]

The following glyphs have components which themselves are component glyphs: * Adieresis [code: found-nested-components]

This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into an integer value.

This can be accomplished by using the 'gftools fix-hinting' command:

# create virtualenv
python3 -m venv venv
# activate virtualenv
source venv/bin/activate
# install gftools
pip install git+https://www.github.com/googlefonts/tools

[code: bad-flags]

This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into an integer value.

This can be accomplished by using the 'gftools fix-hinting' command:

# create virtualenv
python3 -m venv venv
# activate virtualenv
source venv/bin/activate
# install gftools
pip install git+https://www.github.com/googlefonts/tools

[code: bad-flags]

This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into an integer value.

This can be accomplished by using the 'gftools fix-hinting' command:

# create virtualenv
python3 -m venv venv
# activate virtualenv
source venv/bin/activate
# install gftools
pip install git+https://www.github.com/googlefonts/tools

[code: bad-flags]

This is a hinted font, so it must have bit 3 set on the flags of the head table, so that PPEM values will be rounded into an integer value.

This can be accomplished by using the 'gftools fix-hinting' command:

# create virtualenv
python3 -m venv venv
# activate virtualenv
source venv/bin/activate
# install gftools
pip install git+https://www.github.com/googlefonts/tools

[code: bad-flags]

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

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

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

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 + i

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

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

- f + i

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

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

- f + i

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

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

- f + i

- i + j [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]

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]

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 stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]

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 does not have a 'meta' table. [code: lacks-meta-table]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[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: dcaron	Contours detected: 2	Expected: 3

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

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

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

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

[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: fi	Contours detected: 2	Expected: 3

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

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

[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: fi	Contours detected: 2	Expected: 3

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

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

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

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

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

Width = 455: logicalnot, plus

Width = 446: less

Width = 456: multiply, approxequal, equal

Width = 450: divide

Width = 462: minus

Width = 461: lessequal [code: width-outliers]

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

Width = 446: greater, less, plusminus

Width = 444: approxequal, equal

Width = 440: logicalnot

Width = 445: multiply, divide

Width = 466: minus

Width = 460: lessequal [code: width-outliers]

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

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]

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 glyphs have coordinates which are out of bounds: * ('igrave', 247, 502)

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: * ('quotedbl', 83, 419)

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]

No dotted circle glyph present [code: missing-dotted-circle]

No dotted circle glyph present [code: missing-dotted-circle]

No dotted circle glyph present [code: missing-dotted-circle]

No dotted circle glyph present [code: missing-dotted-circle]