If you think a check is flawed or have an idea for a check, please file an issue at https://github.com/fonttools/fontbakery/issues and remember to include a pointer to the repo and branch you're checking.
Summary
💥 ERROR | 🔥 FAIL | ⚠️ WARN | ⏩ SKIP | ℹ️ INFO | ✅ PASS |
---|---|---|---|---|---|
0 | 20 | 59 | 190 | 22 | 398 |
0% | 4% | 11% | 37% | 4% | 77% |
Note: The following loglevels were omitted in this report: SKIP, INFO, PASS, DEBUG
Meaning of check results:
- 💥 An ERROR is something wrong with FontBakery itself, possibly a bug.
- 🔥 A FAIL is a problem with the font that must be fixed.
- ⚠️ A WARN is something that you should consider addressing.
- ℹ️ An INFO result simply prints something useful. Typically stats.
- ✅ A PASS means the font looks good for the given checking routine.
- ⏩ And a SKIP happens when the check does not apply to the given font.
If you get ERRORs, please help us improve the tool by reporting them at our issue tracker.
(but other kinds of bug reports and/or feature requests are also always welcome, of course!)
FontBakery version: 0.9.2
Section: Google Fonts
🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥🔥⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️Checking OS/2 achVendID.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
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]
Check Google Fonts glyph coverage.
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
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]
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
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]
🔥 LibreBaskerville-Bold.ttf
- 🔥 FAIL
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]
Check for codepoints not covered by METADATA subsets.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
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+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+03BC GREEK SMALL LETTER MU: try adding greek
- 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: not included in any glyphset definition
- U+2030 PER MILLE SIGN: not included in any glyphset definition
- 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 tai-tham
- 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
- U+FB06 LATIN SMALL LIGATURE ST: 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]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
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+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+03BC GREEK SMALL LETTER MU: try adding greek
- 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: not included in any glyphset definition
- U+2030 PER MILLE SIGN: not included in any glyphset definition
- 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 tai-tham
- 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
- U+FB06 LATIN SMALL LIGATURE ST: 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]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
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+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+03BC GREEK SMALL LETTER MU: try adding greek
- 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: not included in any glyphset definition
- U+2030 PER MILLE SIGN: not included in any glyphset definition
- 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 tai-tham
- 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
- U+FB06 LATIN SMALL LIGATURE ST: 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]
Check license file has good copyright string.
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
First line in license file is:
"copyright (c) 2012, pablo impallari (www.impallari.com|impallari@gmail.com),"
which does not match the expected format, similar to:
"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
First line in license file is:
"copyright (c) 2012, pablo impallari (www.impallari.com|impallari@gmail.com),"
which does not match the expected format, similar to:
"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]
🔥 LibreBaskerville-Bold.ttf
- 🔥 FAIL
First line in license file is:
"copyright (c) 2012, pablo impallari (www.impallari.com|impallari@gmail.com),"
which does not match the expected format, similar to:
"Copyright 2022 The Familyname Project Authors (git url)" [code: bad-format]
Check copyright namerecords match license file.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
License URL matches License text on name table?
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=14] [code: http-in-license-info]
- ⚠️ WARN
Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
- ⚠️ WARN
For now we're still accepting http URLs, but you should consider using https instead. [code: http]
Description strings in the name table must not exceed 200 characters.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
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]
Font has old ttfautohint applied?
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
ttfautohint used in font = 0.93; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
ttfautohint used in font = 0.93; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
ttfautohint used in font = 0.93; latest = 1.8.4; Need to re-run with the newer version! [code: old-ttfa]
METADATA.pb subsets should be alphabetically ordered.
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'latin', 'latin-ext'] and expected ['latin', 'latin-ext', 'menu'] [code: not-sorted]
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'latin', 'latin-ext'] and expected ['latin', 'latin-ext', 'menu'] [code: not-sorted]
🔥 LibreBaskerville-Bold.ttf
- 🔥 FAIL
METADATA.pb subsets are not sorted in alphabetical order: Got ['menu', 'latin', 'latin-ext'] and expected ['latin', 'latin-ext', 'menu'] [code: not-sorted]
METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
METADATA.pb font full_name = "Libre Baskerville" does not match post_script_name = "LibreBaskerville-Regular" [code: mismatch]
Copyright notices match canonical pattern in METADATA.pb
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
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), copyright (c) 2012, rodrigo fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with reserved font name libre baskerville." [code: bad-notice-format]
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
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), copyright (c) 2012, rodrigo fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with reserved font name libre baskerville." [code: bad-notice-format]
🔥 LibreBaskerville-Bold.ttf
- 🔥 FAIL
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), copyright (c) 2012, rodrigo fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with reserved font name libre baskerville." [code: bad-notice-format]
Copyright notices match canonical pattern in fonts
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
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), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville." [code: bad-notice-format]
- 🔥 FAIL
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), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville." [code: bad-notice-format]
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
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), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville." [code: bad-notice-format]
- 🔥 FAIL
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), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville." [code: bad-notice-format]
🔥 LibreBaskerville-Bold.ttf
- 🔥 FAIL
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), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville." [code: bad-notice-format]
- 🔥 FAIL
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), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville." [code: bad-notice-format]
Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
METADATA.pb: copyright field ("Copyright (c) 2012, Pablo Impallari (www.impallari.com|impallari@gmail.com), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville.") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
METADATA.pb: copyright field ("Copyright (c) 2012, Pablo Impallari (www.impallari.com|impallari@gmail.com), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville.") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
METADATA.pb: copyright field ("Copyright (c) 2012, Pablo Impallari (www.impallari.com|impallari@gmail.com), Copyright (c) 2012, Rodrigo Fuenzalida (www.rfuenzalida.com|hello@rfuenzalida.com), with Reserved Font Name Libre Baskerville.") contains "Reserved Font Name". This is an error except in a few specific rare cases. [code: rfn]
Check font names are correct
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
Regular missing from full name [code: lacks-regular]
Are there caret positions declared for every ligature?
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
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]
Is there kerning info for non-ligated sequences?
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
GPOS table lacks kerning info for the following non-ligated sequences:
- f + f - f + h - h + f - f + l - l + f - f + b - b + f - f + j - j + f - f + k - k + f - f + t - t + f - f + i - i + h - h + l - l + b - b + j - k + t - t + i [code: lacks-kern-info]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
GPOS table lacks kerning info for the following non-ligated sequences:
- f + f - f + h - h + f - f + l - l + f - f + b - b + f - f + j - j + f - f + k - k + f - f + t - t + f - f + i - i + h - h + l - l + b - b + j - k + t - t + i [code: lacks-kern-info]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
GPOS table lacks kerning info for the following non-ligated sequences:
- f + f - f + h - h + f - f + l - l + f - f + b - b + f - f + j - j + f - f + k - k + f - f + t - t + f - f + i - i + h - h + l - l + b - b + j - k + t - t + i [code: lacks-kern-info]
Name table strings must not contain the string 'Reserved Font Name'.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name (Libre Baskerville) that differs from the currently used family name (LibreBaskerville), which is fine. [code: legacy-familyname]
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name (Libre Baskerville) that differs from the currently used family name (LibreBaskerville), which is fine. [code: legacy-familyname]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name (Libre Baskerville) that differs from the currently used family name (LibreBaskerville), which is fine. [code: legacy-familyname]
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name (Libre Baskerville) that differs from the currently used family name (LibreBaskerville), which is fine. [code: legacy-familyname]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name (Libre Baskerville) that differs from the currently used family name (LibreBaskerville), which is fine. [code: legacy-familyname]
- ⚠️ WARN
Name table entry contains "Reserved Font Name" for a family name (Libre Baskerville) that differs from the currently used family name (LibreBaskerville), which is fine. [code: legacy-familyname]
A static fonts directory with at least two fonts must accompany variable fonts
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]
On a family update, the DESCRIPTION.en_us.html file should ideally also be updated.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
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]
Ensure Stylistic Sets have description.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) is set in all fonts.
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Italic.ttf', '/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Regular.ttf', '/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Bold.ttf']. [code: missing-os2-fsselection-bit7]
🔥 LibreBaskerville-Regular.ttf
- 🔥 FAIL
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Italic.ttf', '/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Regular.ttf', '/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Bold.ttf']. [code: missing-os2-fsselection-bit7]
🔥 LibreBaskerville-Bold.ttf
- 🔥 FAIL
OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Italic.ttf', '/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Regular.ttf', '/Users/simon/others-repos/fonts/ofl/librebaskerville/LibreBaskerville-Bold.ttf']. [code: missing-os2-fsselection-bit7]
Ensure fonts have ScriptLangTags declared on the 'meta' table.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
This font file does not have a 'meta' table. [code: lacks-meta-table]
Section: Universal
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩⏩ℹ️ℹ️ℹ️ℹ️ℹ️ℹ️Check font contains no unreachable glyphs
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
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]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
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]
Check if each glyph has the recommended amount of contours.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
- Glyph name: w Contours detected: 2 Expected: 1 - Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: wcircumflex Contours detected: 3 Expected: 2 - Glyph name: wgrave Contours detected: 3 Expected: 2 - Glyph name: wacute Contours detected: 3 Expected: 2 - Glyph name: wdieresis Contours detected: 4 Expected: 3 - Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: w Contours detected: 2 Expected: 1 - Glyph name: wacute Contours detected: 3 Expected: 2 - Glyph name: wcircumflex Contours detected: 3 Expected: 2 - Glyph name: wdieresis Contours detected: 4 Expected: 3 - Glyph name: wgrave Contours detected: 3 Expected: 2
[code: contour-count]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
- Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: uni00AD Contours detected: 1 Expected: 0
[code: contour-count]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct.
The following glyphs do not have the recommended number of contours:
- Glyph name: uni00AD Contours detected: 1 Expected: 0 - Glyph name: uni00AD Contours detected: 1 Expected: 0
[code: contour-count]
Does the font contain a soft hyphen?
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
This font has a 'Soft Hyphen' character. [code: softhyphen]
Check math signs have the same width.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
The most common width is 578 among a set of 1 math glyphs. The following math glyphs have a different width, though:
Width = 618: less
Width = 637: equal
Width = 621: greater
Width = 676: logicalnot
Width = 659: plusminus
Width = 543: multiply
Width = 602: divide
Width = 657: minus [code: width-outliers]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
The most common width is 581 among a set of 2 math glyphs. The following math glyphs have a different width, though:
Width = 550: plus
Width = 620: equal
Width = 625: logicalnot
Width = 634: plusminus, minus
Width = 519: multiply
Width = 599: divide [code: width-outliers]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
The most common width is 593 among a set of 2 math glyphs. The following math glyphs have a different width, though:
Width = 560: plus
Width = 618: equal
Width = 637: logicalnot
Width = 628: plusminus
Width = 524: multiply
Width = 585: divide
Width = 634: minus [code: width-outliers]
Check accent of Lcaron, dcaron, lcaron, tcaron (derived from com.google.fonts/check/alt_caron)
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
dcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
tcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
dcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
tcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
Lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
dcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
lcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
- ⚠️ WARN
tcaron is decomposed and therefore could not be checked. Please check manually. [code: decomposed-outline]
Section: fontbakery.profiles.os2
⚠️⚠️⚠️⏩⏩⏩Check if OS/2 xAvgCharWidth is correct.
⚠️ LibreBaskerville-Italic.ttf
- ⚠️ WARN
OS/2 xAvgCharWidth is 458 but it should be 599 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]
⚠️ LibreBaskerville-Regular.ttf
- ⚠️ WARN
OS/2 xAvgCharWidth is 513 but it should be 635 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]
⚠️ LibreBaskerville-Bold.ttf
- ⚠️ WARN
OS/2 xAvgCharWidth is 526 but it should be 657 which corresponds to the average of the widths of all glyphs in the font. [code: xAvgCharWidth-wrong]
Section: fontbakery.profiles.hhea
🔥Check hhea.caretSlopeRise and hhea.caretSlopeRun
🔥 LibreBaskerville-Italic.ttf
- 🔥 FAIL
hhea.caretSlopeRise and hhea.caretSlopeRun do not match with post.italicAngle. Got: caretSlopeRise 1 and caretSlopeRun 0 Expected: caretSlopeRise 1000 and caretSlopeRun 264 [code: caretslope-mismatch]