Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FB Initial Assessment #3

Open
vv-monsalve opened this issue Oct 5, 2021 · 0 comments
Open

FB Initial Assessment #3

vv-monsalve opened this issue Oct 5, 2021 · 0 comments

Comments

@vv-monsalve
Copy link
Contributor

Fontbakery report

Fontbakery version: 0.8.2

[26] Meow-Formal.ttf
🔥 FAIL: Checking file is named canonically.
--- Rationale ---
A font's filename must be composed in the following manner:
<familyname>-<stylename>.ttf
- Nunito-Regular.ttf,
- Oswald-BoldItalic.ttf
Variable fonts must list the axis tags in alphabetical order in square brackets
and separated by commas:
- Roboto[wdth,wght].ttf
- Familyname-Italic[wght].ttf
  • 🔥 FAIL Style name used in "Meow-Formal.ttf" is not canonical. You should rebuild the font using any of the following style names: "Thin", "ExtraLight", "Light", "Regular", "Medium", "SemiBold", "Bold", "ExtraBold", "Black", "Thin Italic", "ExtraLight Italic", "Light Italic", "Italic", "Medium Italic", "SemiBold Italic", "Bold Italic", "ExtraBold Italic", "Black Italic". [code: bad-static-filename]
🔥 FAIL: Checking OS/2 fsType does not impose restrictions.
--- Rationale ---
The fsType in the OS/2 table is a legacy DRM-related field. Fonts in the Google
Fonts collection must have it set to zero (also known as "Installable
Embedding"). This setting indicates that the fonts can be embedded in documents
and permanently installed by applications on remote systems.
More detailed info is available at:
https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype
  • 🔥 FAIL In this font fsType is set to 4 meaning that:
    The font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.

No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead. [code: drm]

🔥 FAIL: Check `Google Fonts Latin Core` glyph coverage.
--- Rationale ---
Google Fonts expects that fonts in its collection support at least the minimal
set of characters defined in the `GF-latin-core` glyph-set.
  • 🔥 FAIL Missing required codepoints: 0x00A0 (NO-BREAK SPACE) [code: missing-codepoints]
🔥 FAIL: Check license file has good copyright string.
--- Rationale ---
An OFL.txt file's first line should be the font copyright e.g:
"Copyright 2019 The Montserrat Project Authors
(https://github.com/julietaula/montserrat)"
🔥 FAIL: Check copyright namerecords match license file.
--- Rationale ---
A known licensing description must be provided in the NameID 14 (LICENSE
DESCRIPTION) entries of the name table.
The source of truth for this check (to determine which license is in use) is a
file placed side-by-side to your font project including the licensing terms.
Depending on the chosen license, one of the following string snippets is
expected to be found on the NameID 13 (LICENSE DESCRIPTION) entries of the name
table:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.
  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 1 (MACINTOSH) is not specified for that. Value was: "TypeSETit
    End User's License Agreement

Notice to user: By installing this font on your computer, you accept all the terms and conditions of this agreement. If you do not agree with the terms and conditions of this Agreement, destroy the original copies of the Font Software, and cease all use of the Font Software.
This agreement pertains to software program formats which include one or more of the following:
A) "Outline Fonts" (PostScriptTM file for Macintosh) B) "Bitmap Fonts" (related documentation and data which works in combination with the PostScriptTM file) C) "TrueType Fonts" (Suitcase file, or TTF WindowsTM file) D) "OpenType Fonts" (for use on Windows, Macintosh or Linux Operating Systems)
This software contains metric information, digitally encoded machine readable Typeface programs. Listed items A through D underlined above are mutually referred to as "the Font Software." In return for acquiring a license to use the Font Software and documentation, you agree to the following terms and conditions:

  1. USAGE. You agree that you will use the the Font Software to reproduce and display typefaces solely for the customary purposes of printing on devices located at a specific and singular local premise. The maximum number of simultaneous users is specified in the applicable receipt.
  2. Proprietary Rights and obligations. The structure and organization of the Font Software are the valuable and exclusive property of Robert E. Leuschke and his suppliers and distributors. You will not make nor have made, nor permit to be made, any copies of the Font Software or any portions thereof, except one (1) copy solely for backup purposes or such copies as are necessary for the installation of the Font Software in accordance with the terms of this Agreement. Any copies of the Font Software shall contain the same proprietary notices which are contained in or on the Font Software. You agree not to modify, adapt, translate, manipulate, change, reverse engineer, decompile, disassemble, or create derivative works based upon the design of the Font Software. Trademarks shall be used in accordance with accepted trademark practice, including identification of trademark owners name. a) You may embed copies of the font software into your electronic documents for the purpose of printing and viewing the document. No other embedding rights are implied or permitted under this license. b) Access to the Font Software by third parties via access through internet connection is prohibited, unless a separate written agreement has been negotiated.
  3. Assignment. You may not assign your rights under this agreement to a third party. Should you prefer to terminate this Agreement, all copies of the Font Software must be transferred or returned to Robert E. Leuschke, or destroyed. Except as set forth by the above, you may not assign your rights under this Agreement or rent, lease, loan, distribute or otherwise transfer the Font Software. You agree that the Font Software is for use exclusively in accordance with the sovereign laws of the United States of America and will not be shipped, transferred, or exported into any country or used in any manner prohibited by the laws of the United States of America and by the United States Export Administration Act.
  4. No Other Rights. Robert E. Leuschke and his suppliers and distributors retain title and ownership of the Font Software, the media upon which it is recorded, and all subsequent copies of the Font Software, regardless of the form or media in or upon which the original and other copies may exist. Except as stated above, this Agreement does not grant you any rights to intellectual property rights in the Font Software. The use of any trademark as herein authorized does not give you any right of ownership in that trademark.
  5. Term. This license is effective until terminated. Robert E. Leuschke has the right to terminate your license immediately if you fail to comply with any term of this Agreement. Upon any such termination, you will destroy the original copies of the Font Software, and related documentation and cease all use of the Font Software and trademarks.
  6. Limited Warranty. (a) This Limited Warranty and any implied warranties are effective for a period of ninety (90) days from the date of delivery ("Limited Warranty Period") of the Font Software. Evidence of such Limited Warranty Period shall be determined by a copy of your receipt which shall accompany the Font Software. The Font Software shall be free from deliberate errors under normal use and service for a period of ninety (90) days after delivery to you. For the purposes of this agreement, an "error" shall be any flaw in the Font Format which causes improper reproduction when used properly on a computer device. You must do one of the following: Report all errors and return the Font Software to Robert E. Leuschke, or report all errors and destroy any and all of your copies of the Font Software. (b) If the software fails to comply with this warranty, Robert E. Leuschke at his option and discretion, will replace the Font Software media not meeting the warranty. No refunds shall be given for the Font Software. If failure of the Font Software media has resulted from accident, abuse, or misapplication of the product, then Robert E. Leuschke shall not be responsible for the replacement of the Font Software media under this Limited Warranty. (c) Robert E. Leuschke does not and cannot warranty the performance or results you may obtain by using the Font Software or its documentation. The foregoing states the sole and exclusive remedies for Robert E. Leuschke's breach of Warranty. Except for the foregoing Limited Warranty, Robert E. Leuschke makes no Warranties expressed or implied as to non-infringement of third party rights, or fitness for a particular purpose. (d) Some jurisdictions do not allow the exclusion of implied warranties or limitations on how long an implied warranty may last, so the above limitations may not apply to you. This warranty gives you specific legal rights concerning the Font Software and its usage. You may have other rights which vary from state to state and country to country. For further warranty information in regard to your local jurisdiction, contact legal representation in your area.
  7. Limit of liability. (a) You further agree that any such legal liabilities incurred by any parties resulting from a default of this Agreement shall be the sole responsibility of your company. (b) In no way will Robert E. Leuschke be liable to you for any consequential or incidental damages, including any lost profits or lost savings, or for any claim by any party. (c) Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation or exclusion may not apply to you.
  8. Governing Laws. This Agreement will be governed by the laws in force in the State of Missouri, in the United States of America, excluding the application of its conflicts of law rules. This Agreement will not be governed by the United Nations Convention on Contracts for the International Sale of Goods, the application of which is expressly excluded.
  9. Entire Agreement. You acknowledge that you have read this agreement, understand it and that it is the complete and exclusive statement of your agreement with Robert E. Leuschke; which supersedes any prior agreement, oral or written, and any other communications between Robert E. Leuschke and you1 relating to the subject matter of this agreement; and that your obligations under this agreement shall inure to the benefit of Robert E. Leuschke's licensors whose rights are licensed under this agreement. No variation of the terms of this agreement will be enforceable against Robert E. Leuschke unless Robert E. Leuschke gives his expressed, Written and signed consent.
  10. Commitment. Robert E. Leuschke has made deliberate effort to provide within the Font Software the highest quality possible. Continued effort shall be made in good faith to provide such quality. For specific suggestions as to the improvement of the Font Software, please contact Robert E. Leuschke, at:

114 Long and Winding Roa" Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL" [code: wrong]

  • 🔥 FAIL License file OFL.txt exists but NameID 13 (LICENSE DESCRIPTION) value on platform 3 (WINDOWS) is not specified for that. Value was: "TypeSETit
    End User's License Agreement

Notice to user: By installing this font on your computer, you accept all the terms and conditions of this agreement. If you do not agree with the terms and conditions of this Agreement, destroy the original copies of the Font Software, and cease all use of the Font Software.
This agreement pertains to software program formats which include one or more of the following:
A) "Outline Fonts" (PostScriptTM file for Macintosh) B) "Bitmap Fonts" (related documentation and data which works in combination with the PostScriptTM file) C) "TrueType Fonts" (Suitcase file, or TTF WindowsTM file) D) "OpenType Fonts" (for use on Windows, Macintosh or Linux Operating Systems)
This software contains metric information, digitally encoded machine readable Typeface programs. Listed items A through D underlined above are mutually referred to as "the Font Software." In return for acquiring a license to use the Font Software and documentation, you agree to the following terms and conditions:

  1. USAGE. You agree that you will use the the Font Software to reproduce and display typefaces solely for the customary purposes of printing on devices located at a specific and singular local premise. The maximum number of simultaneous users is specified in the applicable receipt.
  2. Proprietary Rights and obligations. The structure and organization of the Font Software are the valuable and exclusive property of Robert E. Leuschke and his suppliers and distributors. You will not make nor have made, nor permit to be made, any copies of the Font Software or any portions thereof, except one (1) copy solely for backup purposes or such copies as are necessary for the installation of the Font Software in accordance with the terms of this Agreement. Any copies of the Font Software shall contain the same proprietary notices which are contained in or on the Font Software. You agree not to modify, adapt, translate, manipulate, change, reverse engineer, decompile, disassemble, or create derivative works based upon the design of the Font Software. Trademarks shall be used in accordance with accepted trademark practice, including identification of trademark owners name. a) You may embed copies of the font software into your electronic documents for the purpose of printing and viewing the document. No other embedding rights are implied or permitted under this license. b) Access to the Font Software by third parties via access through internet connection is prohibited, unless a separate written agreement has been negotiated.
  3. Assignment. You may not assign your rights under this agreement to a third party. Should you prefer to terminate this Agreement, all copies of the Font Software must be transferred or returned to Robert E. Leuschke, or destroyed. Except as set forth by the above, you may not assign your rights under this Agreement or rent, lease, loan, distribute or otherwise transfer the Font Software. You agree that the Font Software is for use exclusively in accordance with the sovereign laws of the United States of America and will not be shipped, transferred, or exported into any country or used in any manner prohibited by the laws of the United States of America and by the United States Export Administration Act.
  4. No Other Rights. Robert E. Leuschke and his suppliers and distributors retain title and ownership of the Font Software, the media upon which it is recorded, and all subsequent copies of the Font Software, regardless of the form or media in or upon which the original and other copies may exist. Except as stated above, this Agreement does not grant you any rights to intellectual property rights in the Font Software. The use of any trademark as herein authorized does not give you any right of ownership in that trademark.
  5. Term. This license is effective until terminated. Robert E. Leuschke has the right to terminate your license immediately if you fail to comply with any term of this Agreement. Upon any such termination, you will destroy the original copies of the Font Software, and related documentation and cease all use of the Font Software and trademarks.
  6. Limited Warranty. (a) This Limited Warranty and any implied warranties are effective for a period of ninety (90) days from the date of delivery ("Limited Warranty Period") of the Font Software. Evidence of such Limited Warranty Period shall be determined by a copy of your receipt which shall accompany the Font Software. The Font Software shall be free from deliberate errors under normal use and service for a period of ninety (90) days after delivery to you. For the purposes of this agreement, an "error" shall be any flaw in the Font Format which causes improper reproduction when used properly on a computer device. You must do one of the following: Report all errors and return the Font Software to Robert E. Leuschke, or report all errors and destroy any and all of your copies of the Font Software. (b) If the software fails to comply with this warranty, Robert E. Leuschke at his option and discretion, will replace the Font Software media not meeting the warranty. No refunds shall be given for the Font Software. If failure of the Font Software media has resulted from accident, abuse, or misapplication of the product, then Robert E. Leuschke shall not be responsible for the replacement of the Font Software media under this Limited Warranty. (c) Robert E. Leuschke does not and cannot warranty the performance or results you may obtain by using the Font Software or its documentation. The foregoing states the sole and exclusive remedies for Robert E. Leuschke's breach of Warranty. Except for the foregoing Limited Warranty, Robert E. Leuschke makes no Warranties expressed or implied as to non-infringement of third party rights, or fitness for a particular purpose. (d) Some jurisdictions do not allow the exclusion of implied warranties or limitations on how long an implied warranty may last, so the above limitations may not apply to you. This warranty gives you specific legal rights concerning the Font Software and its usage. You may have other rights which vary from state to state and country to country. For further warranty information in regard to your local jurisdiction, contact legal representation in your area.
  7. Limit of liability. (a) You further agree that any such legal liabilities incurred by any parties resulting from a default of this Agreement shall be the sole responsibility of your company. (b) In no way will Robert E. Leuschke be liable to you for any consequential or incidental damages, including any lost profits or lost savings, or for any claim by any party. (c) Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so the above limitation or exclusion may not apply to you.
  8. Governing Laws. This Agreement will be governed by the laws in force in the State of Missouri, in the United States of America, excluding the application of its conflicts of law rules. This Agreement will not be governed by the United Nations Convention on Contracts for the International Sale of Goods, the application of which is expressly excluded.
  9. Entire Agreement. You acknowledge that you have read this agreement, understand it and that it is the complete and exclusive statement of your agreement with Robert E. Leuschke; which supersedes any prior agreement, oral or written, and any other communications between Robert E. Leuschke and you1 relating to the subject matter of this agreement; and that your obligations under this agreement shall inure to the benefit of Robert E. Leuschke's licensors whose rights are licensed under this agreement. No variation of the terms of this agreement will be enforceable against Robert E. Leuschke unless Robert E. Leuschke gives his expressed, Written and signed consent.
  10. Commitment. Robert E. Leuschke has made deliberate effort to provide within the Font Software the highest quality possible. Continued effort shall be made in good faith to provide such quality. For specific suggestions as to the improvement of the Font Software, please contact Robert E. Leuschke, at:

114 Long and Winding Roa" Must be changed to "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL" [code: wrong]

🔥 FAIL: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?
--- Rationale ---
Traditionally version 0 'gasp' tables were set so that font sizes below 8 ppem
had no grid fitting but did have antialiasing. From 9-16 ppem, just grid
fitting. And fonts above 17ppem had both antialiasing and grid fitting toggled
on. The use of accelerated graphics cards and higher resolution screens make
this approach obsolete. Microsoft's DirectWrite pushed this even further with
much improved rendering built into the OS and apps.
In this scenario it makes sense to simply toggle all 4 flags ON for all font
sizes.
  • 🔥 FAIL Font is missing the 'gasp' table. Try exporting the font with autohinting enabled.
    If you are dealing with an unhinted font, it can be fixed by running the fonts through the command 'gftools fix-nonhinting'
    GFTools is available at https://pypi.org/project/gftools/ [code: lacks-gasp]
🔥 FAIL: Copyright notices match canonical pattern in fonts
  • com.google.fonts/check/font_copyright

  • 🔥 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) 2017 by Robert E. Leuschke. All rights reserved." [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) 2017 by Robert E. Leuschke. All rights reserved." [code: bad-notice-format]

🔥 FAIL: Check name table: FONT_SUBFAMILY_NAME entries.
🔥 FAIL: Check glyphs do not have components which are themselves components.
--- Rationale ---
There have been bugs rendering variable fonts with nested components.
Additionally, some static fonts with nested components have been reported to
have rendering and printing issues.
For more info, see:
* https://github.com/googlefonts/fontbakery/issues/2961
* https://github.com/arrowtype/recursive/issues/412
  • 🔥 FAIL The following glyphs have components which themselves are component glyphs:
    • uni1EAE
    • uni1EB0
    • uni1EB2
    • uni1EB4
    • uni1EA4
    • uni1EA6
    • uni1EA8
    • uni1EAA
    • uni01C5
    • uni1EBE and 156 more. [code: found-nested-components]
🔥 FAIL: Font enables smart dropout control in "prep" table instructions?
--- Rationale ---
This setup is meant to ensure consistent rendering quality for fonts across all
devices (with different rendering/hinting capabilities).
Below is the snippet of instructions we expect to see in the fonts:
B8 01 FF    PUSHW 0x01FF
85          SCANCTRL (unconditinally turn on
                      dropout control mode)
B0 04       PUSHB 0x04
8D          SCANTYPE (enable smart dropout control)
"Smart dropout control" means activating rules 1, 2 and 5:
Rule 1: If a pixel's center falls within the glyph outline,
        that pixel is turned on.
Rule 2: If a contour falls exactly on a pixel's center,
        that pixel is turned on.
Rule 5: If a scan line between two adjacent pixel centers
        (either vertical or horizontal) is intersected
        by both an on-Transition contour and an off-Transition
        contour and neither of the pixels was already turned on
        by rules 1 and 2, turn on the pixel which is closer to
        the midpoint between the on-Transition contour and
        off-Transition contour. This is "Smart" dropout control.
For more detailed info (such as other rules not enabled in this snippet), please
refer to the TrueType Instruction Set documentation.
  • 🔥 FAIL The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the gftools fix-nonhinting script. [code: lacks-smart-dropout]
🔥 FAIL: Name table entries should not contain line-breaks.
--- Rationale ---
There are some entries on the name table that may include more than one line of
text. The Google Fonts team, though, prefers to keep the name table entries
short and simple without line breaks.
For instance, some designers like to include the full text of a font license in
the "copyright notice" entry, but for the GFonts collection this entry should
only mention year, author and other basic info in a manner enforced by
com.google.fonts/check/font_copyright
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform MACINTOSH contains a line-break. [code: line-break]
  • 🔥 FAIL Name entry LICENSE_DESCRIPTION on platform WINDOWS contains a line-break. [code: line-break]
🔥 FAIL: OS/2.fsSelection bit 7 (USE_TYPO_METRICS) is set in all fonts.
--- Rationale ---
All fonts on the Google Fonts collection should have OS/2.fsSelection bit 7
(USE_TYPO_METRICS) set. This requirement is part of the vertical metrics scheme
established as a Google Fonts policy aiming at a common ground supported by all
major font rendering environments.
For more details, read:
https://github.com/googlefonts/gf-docs/blob/main/VerticalMetrics/README.md
Below is the portion of that document that is most relevant to this check:
Use_Typo_Metrics must be enabled. This will force MS Applications to use the
OS/2 Typo values instead of the Win values. By doing this, we can freely set the
Win values to avoid clipping and control the line height with the typo values.
It has the added benefit of future line height compatibility. When a new script
is added, we simply change the Win values to the new yMin and yMax, without
needing to worry if the line height have changed.
  • 🔥 FAIL OS/2.fsSelection bit 7 (USE_TYPO_METRICS) wasNOT set in the following fonts: ['Meow-Formal.ttf']. [code: missing-os2-fsselection-bit7]
🔥 FAIL: Checking OS/2 usWinAscent & usWinDescent.
--- Rationale ---
A font's winAscent and winDescent values should be greater than the head table's
yMax, abs(yMin) values. If they are less than these values, clipping can occur
on Windows platforms (https://github.com/RedHatBrand/Overpass/issues/33).
If the font includes tall/deep writing systems such as Arabic or Devanagari, the
winAscent and winDescent can be greater than the yMax and abs(yMin) to
accommodate vowel marks.
When the win Metrics are significantly greater than the upm, the linespacing can
appear too loose. To counteract this, enabling the OS/2 fsSelection bit 7
(Use_Typo_Metrics), will force Windows to use the OS/2 typo values instead. This
means the font developer can control the linespacing with the typo values,
whilst avoiding clipping by setting the win values to values greater than the
yMax and abs(yMin).
  • 🔥 FAIL OS/2.usWinAscent value should be equal or greater than 869, but got 850 instead [code: ascent]
  • 🔥 FAIL OS/2.usWinDescent value should be equal or greater than 543, but got 405 instead. [code: descent]
🔥 FAIL: Font contains glyphs for whitespace characters?
🔥 FAIL: Description strings in the name table must not contain copyright info.
  • com.google.fonts/check/name/no_copyright_on_description

  • 🔥 FAIL Some namerecords with ID=10 (NameID.DESCRIPTION) containing copyright info should be removed (perhaps these were added by a longstanding FontLab Studio 5.x bug that copied copyright notices to them.) [code: copyright-on-description]

🔥 FAIL: Does full font name begin with the font family name?
WARN: Checking OS/2 achVendID.
--- Rationale ---
Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is stored
in the achVendID field of the OS/2 table.
Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:
https://docs.microsoft.com/en-us/typography/vendors/
This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.
Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • WARN OS/2 VendorID is 'UKWN', a font editor default. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: bad]
WARN: Check if each glyph has the recommended amount of contours.
--- Rationale ---
Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be
constructured in a handful of ways. This means a glyph's contour count will only
differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3
contours, depending on whether its double story or single story.
However, a quotedbl should have 2 contours, unless the font belongs to a display
family.
This check currently does not cover variable fonts because there's plenty of
alternative ways of constructing glyphs with multiple outlines for each feature
in a VarFont. The expected contour count data for this check is currently
optimized for the typical construction of glyphs in static fonts.
  • 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: percent Contours detected: 4 Expected: 5
Glyph name: five Contours detected: 2 Expected: 1
Glyph name: eight Contours detected: 2 Expected: 3
Glyph name: at Contours detected: 1 Expected: 2
Glyph name: A Contours detected: 3 Expected: 2
Glyph name: C Contours detected: 2 Expected: 1
Glyph name: D Contours detected: 3 Expected: 2
Glyph name: E Contours detected: 2 Expected: 1
Glyph name: G Contours detected: 3 Expected: 1
Glyph name: J Contours detected: 2 Expected: 1
Glyph name: L Contours detected: 3 Expected: 1
Glyph name: O Contours detected: 3 Expected: 2
Glyph name: Y Contours detected: 2 Expected: 1
Glyph name: Z Contours detected: 3 Expected: 1
Glyph name: a Contours detected: 1 Expected: 2
Glyph name: d Contours detected: 3 Expected: 2
Glyph name: f Contours detected: 3 Expected: 1
Glyph name: h Contours detected: 2 Expected: 1
Glyph name: j Contours detected: 3 Expected: 2
Glyph name: l Contours detected: 2 Expected: 1
Glyph name: o Contours detected: 3 Expected: 2
Glyph name: p Contours detected: 3 Expected: 2
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: z Contours detected: 2 Expected: 1
Glyph name: ordfeminine Contours detected: 1 Expected: 2 or 3
Glyph name: Agrave Contours detected: 4 Expected: 3
Glyph name: Aacute Contours detected: 4 Expected: 3
Glyph name: Acircumflex Contours detected: 4 Expected: 3
Glyph name: Atilde Contours detected: 4 Expected: 3
Glyph name: Adieresis Contours detected: 5 Expected: 4
Glyph name: Aring Contours detected: 5 Expected: 3 or 4
Glyph name: AE Contours detected: 4 Expected: 2
Glyph name: Ccedilla Contours detected: 3 Expected: 1 or 2
Glyph name: Egrave Contours detected: 3 Expected: 2
Glyph name: Eacute Contours detected: 3 Expected: 2
Glyph name: Ecircumflex Contours detected: 3 Expected: 2
Glyph name: Edieresis Contours detected: 4 Expected: 3
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Ograve Contours detected: 4 Expected: 3
Glyph name: Oacute Contours detected: 4 Expected: 3
Glyph name: Ocircumflex Contours detected: 4 Expected: 3
Glyph name: Otilde Contours detected: 4 Expected: 3
Glyph name: Odieresis Contours detected: 5 Expected: 4
Glyph name: Oslash Contours detected: 6 Expected: 2 or 3
Glyph name: Yacute Contours detected: 3 Expected: 2
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: agrave Contours detected: 2 Expected: 3
Glyph name: aacute Contours detected: 2 Expected: 3
Glyph name: acircumflex Contours detected: 2 Expected: 3
Glyph name: atilde Contours detected: 2 Expected: 3
Glyph name: adieresis Contours detected: 3 Expected: 4
Glyph name: aring Contours detected: 3 Expected: 4
Glyph name: eth Contours detected: 1 Expected: 2
Glyph name: ograve Contours detected: 4 Expected: 3
Glyph name: oacute Contours detected: 4 Expected: 3
Glyph name: ocircumflex Contours detected: 4 Expected: 3
Glyph name: otilde Contours detected: 4 Expected: 3
Glyph name: odieresis Contours detected: 5 Expected: 4
Glyph name: oslash Contours detected: 5 Expected: 3
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: Amacron Contours detected: 4 Expected: 3
Glyph name: amacron Contours detected: 2 Expected: 3
Glyph name: Abreve Contours detected: 4 Expected: 3
Glyph name: abreve Contours detected: 2 Expected: 3
Glyph name: Aogonek Contours detected: 4 Expected: 2 or 3
Glyph name: aogonek Contours detected: 1 Expected: 2
Glyph name: Cacute Contours detected: 3 Expected: 2
Glyph name: Ccircumflex Contours detected: 3 Expected: 2
Glyph name: Cdotaccent Contours detected: 3 Expected: 2
Glyph name: Ccaron Contours detected: 3 Expected: 2
Glyph name: Dcaron Contours detected: 4 Expected: 3
Glyph name: dcaron Contours detected: 4 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: Emacron Contours detected: 3 Expected: 2
Glyph name: Ebreve Contours detected: 3 Expected: 2
Glyph name: Edotaccent Contours detected: 3 Expected: 2
Glyph name: Eogonek Contours detected: 3 Expected: 1 or 2
Glyph name: Ecaron Contours detected: 3 Expected: 2
Glyph name: Gcircumflex Contours detected: 4 Expected: 2
Glyph name: Gbreve Contours detected: 4 Expected: 2
Glyph name: Gdotaccent Contours detected: 4 Expected: 2
Glyph name: uni0122 Contours detected: 4 Expected: 2
Glyph name: hcircumflex Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 3 Expected: 1
Glyph name: Jcircumflex Contours detected: 3 Expected: 2
Glyph name: jcircumflex Contours detected: 3 Expected: 2
Glyph name: Lacute Contours detected: 4 Expected: 2
Glyph name: lacute Contours detected: 3 Expected: 2
Glyph name: uni013B Contours detected: 4 Expected: 2
Glyph name: uni013C Contours detected: 3 Expected: 2
Glyph name: Lcaron Contours detected: 4 Expected: 2
Glyph name: lcaron Contours detected: 3 Expected: 2
Glyph name: Ldot Contours detected: 4 Expected: 2
Glyph name: Lslash Contours detected: 3 Expected: 1
Glyph name: lslash Contours detected: 2 Expected: 1
Glyph name: Omacron Contours detected: 4 Expected: 3
Glyph name: omacron Contours detected: 4 Expected: 3
Glyph name: Obreve Contours detected: 4 Expected: 3
Glyph name: obreve Contours detected: 4 Expected: 3
Glyph name: Ohungarumlaut Contours detected: 5 Expected: 4
Glyph name: ohungarumlaut Contours detected: 5 Expected: 4
Glyph name: OE Contours detected: 4 Expected: 2
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: Ycircumflex Contours detected: 3 Expected: 2
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: Ydieresis Contours detected: 4 Expected: 3
Glyph name: Zacute Contours detected: 4 Expected: 2
Glyph name: zacute Contours detected: 3 Expected: 2
Glyph name: Zdotaccent Contours detected: 4 Expected: 2
Glyph name: zdotaccent Contours detected: 3 Expected: 2
Glyph name: Zcaron Contours detected: 4 Expected: 2
Glyph name: zcaron Contours detected: 3 Expected: 2
Glyph name: Ohorn Contours detected: 4 Expected: 2 or 3
Glyph name: ohorn Contours detected: 4 Expected: 2
Glyph name: Uhorn Contours detected: 2 Expected: 1
Glyph name: uhorn Contours detected: 2 Expected: 1
Glyph name: uni01C4 Contours detected: 5 Expected: 4
Glyph name: uni01C5 Contours detected: 6 Expected: 4
Glyph name: uni01C6 Contours detected: 6 Expected: 4
Glyph name: uni01C7 Contours detected: 4 Expected: 2
Glyph name: uni01C8 Contours detected: 6 Expected: 3
Glyph name: uni01C9 Contours detected: 4 Expected: 3
Glyph name: uni01CB Contours detected: 4 Expected: 3
Glyph name: uni01CD Contours detected: 4 Expected: 3
Glyph name: uni01CE Contours detected: 2 Expected: 3
Glyph name: uni01D1 Contours detected: 4 Expected: 3
Glyph name: uni01D5 Contours detected: 2 Expected: 4
Glyph name: uni01D9 Contours detected: 2 Expected: 4
Glyph name: uni01DB Contours detected: 3 Expected: 4
Glyph name: Gcaron Contours detected: 4 Expected: 2
Glyph name: uni01EA Contours detected: 4 Expected: 2
Glyph name: uni01EB Contours detected: 3 Expected: 2
Glyph name: Aringacute Contours detected: 6 Expected: 3, 4 or 5
Glyph name: AEacute Contours detected: 5 Expected: 3
Glyph name: aeacute Contours detected: 3 Expected: 4
Glyph name: Oslashacute Contours detected: 7 Expected: 4
Glyph name: oslashacute Contours detected: 6 Expected: 4
Glyph name: uni0200 Contours detected: 5 Expected: 4
Glyph name: uni0201 Contours detected: 3 Expected: 4
Glyph name: uni0202 Contours detected: 4 Expected: 3
Glyph name: uni0203 Contours detected: 2 Expected: 3
Glyph name: uni0204 Contours detected: 4 Expected: 3
Glyph name: uni0206 Contours detected: 3 Expected: 2
Glyph name: uni020C Contours detected: 5 Expected: 4
Glyph name: uni020D Contours detected: 5 Expected: 4
Glyph name: uni020E Contours detected: 4 Expected: 3
Glyph name: uni020F Contours detected: 4 Expected: 3
Glyph name: uni022A Contours detected: 4 Expected: 5
Glyph name: uni022B Contours detected: 4 Expected: 5
Glyph name: uni022C Contours detected: 5 Expected: 4
Glyph name: uni022D Contours detected: 5 Expected: 4
Glyph name: uni0232 Contours detected: 3 Expected: 2
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni0237 Contours detected: 2 Expected: 1
Glyph name: uni1EA0 Contours detected: 4 Expected: 3
Glyph name: uni1EA1 Contours detected: 2 Expected: 3
Glyph name: uni1EA2 Contours detected: 4 Expected: 3
Glyph name: uni1EA3 Contours detected: 2 Expected: 3
Glyph name: uni1EA4 Contours detected: 5 Expected: 4
Glyph name: uni1EA5 Contours detected: 3 Expected: 4
Glyph name: uni1EA6 Contours detected: 5 Expected: 4
Glyph name: uni1EA7 Contours detected: 3 Expected: 4
Glyph name: uni1EA8 Contours detected: 5 Expected: 4
Glyph name: uni1EA9 Contours detected: 3 Expected: 4
Glyph name: uni1EAA Contours detected: 5 Expected: 4
Glyph name: uni1EAB Contours detected: 3 Expected: 4
Glyph name: uni1EAC Contours detected: 5 Expected: 4
Glyph name: uni1EAD Contours detected: 3 Expected: 4
Glyph name: uni1EAE Contours detected: 5 Expected: 4
Glyph name: uni1EAF Contours detected: 3 Expected: 4
Glyph name: uni1EB0 Contours detected: 5 Expected: 4
Glyph name: uni1EB1 Contours detected: 3 Expected: 4
Glyph name: uni1EB2 Contours detected: 5 Expected: 4
Glyph name: uni1EB3 Contours detected: 3 Expected: 4
Glyph name: uni1EB4 Contours detected: 5 Expected: 4
Glyph name: uni1EB5 Contours detected: 3 Expected: 4
Glyph name: uni1EB6 Contours detected: 5 Expected: 4
Glyph name: uni1EB7 Contours detected: 3 Expected: 4
Glyph name: uni1EB8 Contours detected: 3 Expected: 2
Glyph name: uni1EBA Contours detected: 3 Expected: 2
Glyph name: uni1EBC Contours detected: 3 Expected: 2
Glyph name: uni1EBE Contours detected: 4 Expected: 3
Glyph name: uni1EC0 Contours detected: 4 Expected: 3
Glyph name: uni1EC2 Contours detected: 4 Expected: 3
Glyph name: uni1EC4 Contours detected: 4 Expected: 3
Glyph name: uni1EC6 Contours detected: 4 Expected: 3
Glyph name: uni1ECC Contours detected: 4 Expected: 3
Glyph name: uni1ECD Contours detected: 4 Expected: 3
Glyph name: uni1ECE Contours detected: 4 Expected: 3
Glyph name: uni1ECF Contours detected: 4 Expected: 3
Glyph name: uni1ED0 Contours detected: 5 Expected: 4
Glyph name: uni1ED1 Contours detected: 5 Expected: 4
Glyph name: uni1ED2 Contours detected: 5 Expected: 4
Glyph name: uni1ED3 Contours detected: 5 Expected: 4
Glyph name: uni1ED4 Contours detected: 5 Expected: 4
Glyph name: uni1ED5 Contours detected: 5 Expected: 4
Glyph name: uni1ED6 Contours detected: 5 Expected: 4
Glyph name: uni1ED7 Contours detected: 5 Expected: 4
Glyph name: uni1ED8 Contours detected: 5 Expected: 4
Glyph name: uni1ED9 Contours detected: 5 Expected: 4
Glyph name: uni1EDA Contours detected: 5 Expected: 3 or 4
Glyph name: uni1EDB Contours detected: 5 Expected: 3
Glyph name: uni1EDD Contours detected: 4 Expected: 3
Glyph name: uni1EDF Contours detected: 4 Expected: 3
Glyph name: uni1EE0 Contours detected: 5 Expected: 3 or 4
Glyph name: uni1EE1 Contours detected: 5 Expected: 3
Glyph name: uni1EE2 Contours detected: 5 Expected: 3 or 4
Glyph name: uni1EE3 Contours detected: 5 Expected: 3
Glyph name: uni1EE8 Contours detected: 3 Expected: 2
Glyph name: uni1EE9 Contours detected: 3 Expected: 2
Glyph name: uni1EEE Contours detected: 3 Expected: 2
Glyph name: uni1EEF Contours detected: 3 Expected: 2
Glyph name: uni1EF0 Contours detected: 3 Expected: 2
Glyph name: uni1EF1 Contours detected: 3 Expected: 2
Glyph name: Ygrave Contours detected: 3 Expected: 2
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: uni1EF4 Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF6 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF8 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2
Glyph name: lira Contours detected: 2 Expected: 1
Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7
Glyph name: uni20B1 Contours detected: 3 Expected: 1, 2 or 4
Glyph name: uni20BD Contours detected: 1 Expected: 2
Glyph name: estimated Contours detected: 5 Expected: 2
Glyph name: partialdiff Contours detected: 1 Expected: 2
Glyph name: f_f Contours detected: 6 Expected: 1 or 2
Glyph name: fi Contours detected: 5 Expected: 1, 2 or 3
Glyph name: fl Contours detected: 4 Expected: 1 or 2
Glyph name: f_f_i Contours detected: 8 Expected: 1, 2, 3 or 4
Glyph name: f_f_l Contours detected: 8 Expected: 1, 2 or 3
Glyph name: A Contours detected: 3 Expected: 2
Glyph name: AE Contours detected: 4 Expected: 2
Glyph name: AEacute Contours detected: 5 Expected: 3
Glyph name: Aacute Contours detected: 4 Expected: 3
Glyph name: Abreve Contours detected: 4 Expected: 3
Glyph name: Acircumflex Contours detected: 4 Expected: 3
Glyph name: Adieresis Contours detected: 5 Expected: 4
Glyph name: Agrave Contours detected: 4 Expected: 3
Glyph name: Amacron Contours detected: 4 Expected: 3
Glyph name: Aogonek Contours detected: 4 Expected: 2 or 3
Glyph name: Aring Contours detected: 5 Expected: 3 or 4
Glyph name: Aringacute Contours detected: 6 Expected: 3, 4 or 5
Glyph name: Atilde Contours detected: 4 Expected: 3
Glyph name: C Contours detected: 2 Expected: 1
Glyph name: Cacute Contours detected: 3 Expected: 2
Glyph name: Ccaron Contours detected: 3 Expected: 2
Glyph name: Ccedilla Contours detected: 3 Expected: 1 or 2
Glyph name: Ccircumflex Contours detected: 3 Expected: 2
Glyph name: Cdotaccent Contours detected: 3 Expected: 2
Glyph name: D Contours detected: 3 Expected: 2
Glyph name: Dcaron Contours detected: 4 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: E Contours detected: 2 Expected: 1
Glyph name: Eacute Contours detected: 3 Expected: 2
Glyph name: Ebreve Contours detected: 3 Expected: 2
Glyph name: Ecaron Contours detected: 3 Expected: 2
Glyph name: Ecircumflex Contours detected: 3 Expected: 2
Glyph name: Edieresis Contours detected: 4 Expected: 3
Glyph name: Edotaccent Contours detected: 3 Expected: 2
Glyph name: Egrave Contours detected: 3 Expected: 2
Glyph name: Emacron Contours detected: 3 Expected: 2
Glyph name: Eogonek Contours detected: 3 Expected: 1 or 2
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: G Contours detected: 3 Expected: 1
Glyph name: Gbreve Contours detected: 4 Expected: 2
Glyph name: Gcaron Contours detected: 4 Expected: 2
Glyph name: Gcircumflex Contours detected: 4 Expected: 2
Glyph name: Gdotaccent Contours detected: 4 Expected: 2
Glyph name: J Contours detected: 2 Expected: 1
Glyph name: Jcircumflex Contours detected: 3 Expected: 2
Glyph name: L Contours detected: 3 Expected: 1
Glyph name: Lacute Contours detected: 4 Expected: 2
Glyph name: Lcaron Contours detected: 4 Expected: 2
Glyph name: Ldot Contours detected: 4 Expected: 2
Glyph name: Lslash Contours detected: 3 Expected: 1
Glyph name: O Contours detected: 3 Expected: 2
Glyph name: OE Contours detected: 4 Expected: 2
Glyph name: Oacute Contours detected: 4 Expected: 3
Glyph name: Ocircumflex Contours detected: 4 Expected: 3
Glyph name: Odieresis Contours detected: 5 Expected: 4
Glyph name: Ograve Contours detected: 4 Expected: 3
Glyph name: Ohorn Contours detected: 4 Expected: 2 or 3
Glyph name: Ohungarumlaut Contours detected: 5 Expected: 4
Glyph name: Omacron Contours detected: 4 Expected: 3
Glyph name: Oslash Contours detected: 6 Expected: 2 or 3
Glyph name: Oslashacute Contours detected: 7 Expected: 4
Glyph name: Otilde Contours detected: 4 Expected: 3
Glyph name: Uhorn Contours detected: 2 Expected: 1
Glyph name: Uogonek Contours detected: 2 Expected: 1
Glyph name: Y Contours detected: 2 Expected: 1
Glyph name: Yacute Contours detected: 3 Expected: 2
Glyph name: Ycircumflex Contours detected: 3 Expected: 2
Glyph name: Ydieresis Contours detected: 4 Expected: 3
Glyph name: Ygrave Contours detected: 3 Expected: 2
Glyph name: Z Contours detected: 3 Expected: 1
Glyph name: Zacute Contours detected: 4 Expected: 2
Glyph name: Zcaron Contours detected: 4 Expected: 2
Glyph name: Zdotaccent Contours detected: 4 Expected: 2
Glyph name: a Contours detected: 1 Expected: 2
Glyph name: aacute Contours detected: 2 Expected: 3
Glyph name: abreve Contours detected: 2 Expected: 3
Glyph name: acircumflex Contours detected: 2 Expected: 3
Glyph name: adieresis Contours detected: 3 Expected: 4
Glyph name: aeacute Contours detected: 3 Expected: 4
Glyph name: agrave Contours detected: 2 Expected: 3
Glyph name: amacron Contours detected: 2 Expected: 3
Glyph name: aogonek Contours detected: 1 Expected: 2
Glyph name: aring Contours detected: 3 Expected: 4
Glyph name: at Contours detected: 1 Expected: 2
Glyph name: atilde Contours detected: 2 Expected: 3
Glyph name: d Contours detected: 3 Expected: 2
Glyph name: dcaron Contours detected: 4 Expected: 3
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: eight Contours detected: 2 Expected: 3
Glyph name: estimated Contours detected: 5 Expected: 2
Glyph name: eth Contours detected: 1 Expected: 2
Glyph name: f Contours detected: 3 Expected: 1
Glyph name: f_f Contours detected: 6 Expected: 1 or 2
Glyph name: f_f_i Contours detected: 8 Expected: 1, 2, 3 or 4
Glyph name: f_f_l Contours detected: 8 Expected: 1, 2 or 3
Glyph name: fi Contours detected: 5 Expected: 3
Glyph name: five Contours detected: 2 Expected: 1
Glyph name: fl Contours detected: 4 Expected: 2
Glyph name: germandbls Contours detected: 2 Expected: 1
Glyph name: h Contours detected: 2 Expected: 1
Glyph name: hbar Contours detected: 3 Expected: 1
Glyph name: hcircumflex Contours detected: 3 Expected: 2
Glyph name: j Contours detected: 3 Expected: 2
Glyph name: jcircumflex Contours detected: 3 Expected: 2
Glyph name: l Contours detected: 2 Expected: 1
Glyph name: lacute Contours detected: 3 Expected: 2
Glyph name: lcaron Contours detected: 3 Expected: 2
Glyph name: lira Contours detected: 2 Expected: 1
Glyph name: lslash Contours detected: 2 Expected: 1
Glyph name: o Contours detected: 3 Expected: 2
Glyph name: oacute Contours detected: 4 Expected: 3
Glyph name: ocircumflex Contours detected: 4 Expected: 3
Glyph name: odieresis Contours detected: 5 Expected: 4
Glyph name: ograve Contours detected: 4 Expected: 3
Glyph name: ohorn Contours detected: 4 Expected: 2
Glyph name: ohungarumlaut Contours detected: 5 Expected: 4
Glyph name: omacron Contours detected: 4 Expected: 3
Glyph name: ordfeminine Contours detected: 1 Expected: 2 or 3
Glyph name: oslash Contours detected: 5 Expected: 3
Glyph name: oslashacute Contours detected: 6 Expected: 4
Glyph name: otilde Contours detected: 4 Expected: 3
Glyph name: p Contours detected: 3 Expected: 2
Glyph name: partialdiff Contours detected: 1 Expected: 2
Glyph name: percent Contours detected: 4 Expected: 5
Glyph name: uhorn Contours detected: 2 Expected: 1
Glyph name: uni0122 Contours detected: 4 Expected: 2
Glyph name: uni013B Contours detected: 4 Expected: 2
Glyph name: uni013C Contours detected: 3 Expected: 2
Glyph name: uni01C4 Contours detected: 5 Expected: 4
Glyph name: uni01C5 Contours detected: 6 Expected: 4
Glyph name: uni01C6 Contours detected: 6 Expected: 4
Glyph name: uni01C7 Contours detected: 4 Expected: 2
Glyph name: uni01C8 Contours detected: 6 Expected: 3
Glyph name: uni01C9 Contours detected: 4 Expected: 3
Glyph name: uni01CB Contours detected: 4 Expected: 3
Glyph name: uni01CD Contours detected: 4 Expected: 3
Glyph name: uni01CE Contours detected: 2 Expected: 3
Glyph name: uni01D1 Contours detected: 4 Expected: 3
Glyph name: uni01D5 Contours detected: 2 Expected: 4
Glyph name: uni01D9 Contours detected: 2 Expected: 4
Glyph name: uni01DB Contours detected: 3 Expected: 4
Glyph name: uni022A Contours detected: 4 Expected: 5
Glyph name: uni022B Contours detected: 4 Expected: 5
Glyph name: uni022C Contours detected: 5 Expected: 4
Glyph name: uni022D Contours detected: 5 Expected: 4
Glyph name: uni0232 Contours detected: 3 Expected: 2
Glyph name: uni0233 Contours detected: 3 Expected: 2
Glyph name: uni0237 Contours detected: 2 Expected: 1
Glyph name: uni1EA0 Contours detected: 4 Expected: 3
Glyph name: uni1EA1 Contours detected: 2 Expected: 3
Glyph name: uni1EA2 Contours detected: 4 Expected: 3
Glyph name: uni1EA3 Contours detected: 2 Expected: 3
Glyph name: uni1EA4 Contours detected: 5 Expected: 4
Glyph name: uni1EA5 Contours detected: 3 Expected: 4
Glyph name: uni1EA6 Contours detected: 5 Expected: 4
Glyph name: uni1EA7 Contours detected: 3 Expected: 4
Glyph name: uni1EA8 Contours detected: 5 Expected: 4
Glyph name: uni1EA9 Contours detected: 3 Expected: 4
Glyph name: uni1EAA Contours detected: 5 Expected: 4
Glyph name: uni1EAB Contours detected: 3 Expected: 4
Glyph name: uni1EAC Contours detected: 5 Expected: 4
Glyph name: uni1EAD Contours detected: 3 Expected: 4
Glyph name: uni1EAE Contours detected: 5 Expected: 4
Glyph name: uni1EAF Contours detected: 3 Expected: 4
Glyph name: uni1EB0 Contours detected: 5 Expected: 4
Glyph name: uni1EB1 Contours detected: 3 Expected: 4
Glyph name: uni1EB2 Contours detected: 5 Expected: 4
Glyph name: uni1EB3 Contours detected: 3 Expected: 4
Glyph name: uni1EB4 Contours detected: 5 Expected: 4
Glyph name: uni1EB5 Contours detected: 3 Expected: 4
Glyph name: uni1EB6 Contours detected: 5 Expected: 4
Glyph name: uni1EB7 Contours detected: 3 Expected: 4
Glyph name: uni1EB8 Contours detected: 3 Expected: 2
Glyph name: uni1EBA Contours detected: 3 Expected: 2
Glyph name: uni1EBC Contours detected: 3 Expected: 2
Glyph name: uni1EBE Contours detected: 4 Expected: 3
Glyph name: uni1EC0 Contours detected: 4 Expected: 3
Glyph name: uni1EC2 Contours detected: 4 Expected: 3
Glyph name: uni1EC4 Contours detected: 4 Expected: 3
Glyph name: uni1EC6 Contours detected: 4 Expected: 3
Glyph name: uni1ECC Contours detected: 4 Expected: 3
Glyph name: uni1ECD Contours detected: 4 Expected: 3
Glyph name: uni1ECE Contours detected: 4 Expected: 3
Glyph name: uni1ECF Contours detected: 4 Expected: 3
Glyph name: uni1ED0 Contours detected: 5 Expected: 4
Glyph name: uni1ED1 Contours detected: 5 Expected: 4
Glyph name: uni1ED2 Contours detected: 5 Expected: 4
Glyph name: uni1ED3 Contours detected: 5 Expected: 4
Glyph name: uni1ED4 Contours detected: 5 Expected: 4
Glyph name: uni1ED5 Contours detected: 5 Expected: 4
Glyph name: uni1ED6 Contours detected: 5 Expected: 4
Glyph name: uni1ED7 Contours detected: 5 Expected: 4
Glyph name: uni1ED8 Contours detected: 5 Expected: 4
Glyph name: uni1ED9 Contours detected: 5 Expected: 4
Glyph name: uni1EDA Contours detected: 5 Expected: 3 or 4
Glyph name: uni1EDB Contours detected: 5 Expected: 3
Glyph name: uni1EDD Contours detected: 4 Expected: 3
Glyph name: uni1EDF Contours detected: 4 Expected: 3
Glyph name: uni1EE0 Contours detected: 5 Expected: 3 or 4
Glyph name: uni1EE1 Contours detected: 5 Expected: 3
Glyph name: uni1EE2 Contours detected: 5 Expected: 3 or 4
Glyph name: uni1EE3 Contours detected: 5 Expected: 3
Glyph name: uni1EE8 Contours detected: 3 Expected: 2
Glyph name: uni1EE9 Contours detected: 3 Expected: 2
Glyph name: uni1EEE Contours detected: 3 Expected: 2
Glyph name: uni1EEF Contours detected: 3 Expected: 2
Glyph name: uni1EF0 Contours detected: 3 Expected: 2
Glyph name: uni1EF1 Contours detected: 3 Expected: 2
Glyph name: uni1EF4 Contours detected: 3 Expected: 2
Glyph name: uni1EF5 Contours detected: 3 Expected: 2
Glyph name: uni1EF6 Contours detected: 3 Expected: 2
Glyph name: uni1EF7 Contours detected: 3 Expected: 2
Glyph name: uni1EF8 Contours detected: 3 Expected: 2
Glyph name: uni1EF9 Contours detected: 3 Expected: 2
Glyph name: uni20A9 Contours detected: 6 Expected: 1, 3, 4 or 7
Glyph name: uni20B1 Contours detected: 3 Expected: 1, 2 or 4
Glyph name: uni20BD Contours detected: 1 Expected: 2
Glyph name: y Contours detected: 2 Expected: 1
Glyph name: yacute Contours detected: 3 Expected: 2
Glyph name: ycircumflex Contours detected: 3 Expected: 2
Glyph name: ydieresis Contours detected: 4 Expected: 3
Glyph name: ygrave Contours detected: 3 Expected: 2
Glyph name: z Contours detected: 2 Expected: 1
Glyph name: zacute Contours detected: 3 Expected: 2
Glyph name: zcaron Contours detected: 3 Expected: 2
Glyph name: zdotaccent Contours detected: 3 Expected: 2 [code: contour-count]

WARN: Are there caret positions declared for every ligature?
--- Rationale ---
All ligatures in a font must have corresponding caret (text cursor) positions
defined in the GDEF table, otherwhise, users may experience issues with caret
rendering.
If using GlyphsApp or UFOs, ligature carets can be defined as anchors with names
starting with 'caret_'. These can be compiled with fontmake as of version
v2.4.0.
  • WARN This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]
WARN: Is there kerning info for non-ligated sequences?
--- Rationale ---
Fonts with ligatures should have kerning on the corresponding non-ligated
sequences for text where ligatures aren't used (eg
https://github.com/impallari/Raleway/issues/14).
  • WARN GPOS table lacks kerning info for the following non-ligated sequences:

    • f + f
    • f + i
    • i + f
    • f + l
    • l + f
    • i + l

    [code: lacks-kern-info]

WARN: Ensure Stylistic Sets have description.
--- Rationale ---
Stylistic sets should provide description text. Programs such as InDesign,
TextEdit and Inkscape use that info to display to the users so that they know
what a given stylistic set offers.
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss01 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss02 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss03 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss04 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss05 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
  • WARN The stylistic set ss06 lacks a description string on the 'name' table. [code: missing-description]
WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.
--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.
  • WARN This font file does not have a 'meta' table. [code: lacks-meta-table]
WARN: Does the font have a DSIG table?
--- Rationale ---
Microsoft Office 2013 and below products expect fonts to have a digital
signature declared in a DSIG table in order to implement OpenType features. The
EOL date for Microsoft Office 2013 products is 4/11/2023. This issue does not
impact Microsoft Office 2016 and above products.
As we approach the EOL date, it is now considered better to completely remove
the table.
But if you still want your font to support OpenType features on Office 2013,
then you may find it handy to add a fake signature on a dummy DSIG table by
running one of the helper scripts provided at
https://github.com/googlefonts/gftools
Reference: https://github.com/googlefonts/fontbakery/issues/1845
  • WARN This font has a digital signature (DSIG table) which is only required - even if only a dummy 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]
WARN: Do any segments have colinear vectors?
--- Rationale ---
This check looks for consecutive line segments which have the same angle. This
normally happens if an outline point has been added by accident.
This check is not run for variable fonts, as they may legitimately have colinear
vectors.
  • WARN The following glyphs have colinear vectors:
    • P (U+0050): L<<601.0,279.0>--<546.0,201.0>> -> L<<546.0,201.0>--<538.0,190.0>>
    • X (U+0058): L<<497.0,302.0>--<495.0,267.0>> -> L<<495.0,267.0>--<493.0,234.0>>
    • Z (U+005A): L<<496.0,-55.0>--<469.0,-41.0>> -> L<<469.0,-41.0>--<442.0,-28.0>>
    • Zacute (U+0179): L<<496.0,-55.0>--<469.0,-41.0>> -> L<<469.0,-41.0>--<442.0,-28.0>>
    • Zcaron (U+017D): L<<496.0,-55.0>--<469.0,-41.0>> -> L<<469.0,-41.0>--<442.0,-28.0>>
    • Zdotaccent (U+017B): L<<496.0,-55.0>--<469.0,-41.0>> -> L<<469.0,-41.0>--<442.0,-28.0>>
    • cent (U+00A2): L<<419.0,207.0>--<474.0,267.0>> -> L<<474.0,267.0>--<493.0,289.0>>
    • f_f_i (U+FB03): L<<876.0,62.0>--<931.0,122.0>> -> L<<931.0,122.0>--<950.0,144.0>>
    • f_f_l (U+FB04): L<<1033.0,62.0>--<1088.0,122.0>> -> L<<1088.0,122.0>--<1107.0,144.0>>
    • germandbls (U+00DF): L<<163.0,112.0>--<130.0,56.0>> -> L<<130.0,56.0>--<95.0,-3.0>> and 49 more. [code: found-colinear-vectors]
WARN: Do outlines contain any jaggy segments?
--- Rationale ---
This check heuristically detects outline segments which form a particularly
small angle, indicative of an outline error. This may cause false positives in
cases such as extreme ink traps, so should be regarded as advisory and backed up
by manual inspection.
  • WARN The following glyphs have jaggy segments:
    • A (U+0041): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • AE (U+00C6): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • AEacute (U+01FC): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Aacute (U+00C1): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Abreve (U+0102): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Acircumflex (U+00C2): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Adieresis (U+00C4): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Agrave (U+00C0): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Amacron (U+0100): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917
    • Aogonek (U+0104): B<<650.0,317.0>-<652.0,319.0>-<653.0,319.0>>/B<<653.0,319.0>-<618.0,315.0>-<569.0,315.0>> = 6.519801751656917 and 35 more. [code: found-jaggy-segments]
WARN: Do outlines contain any semi-vertical or semi-horizontal lines?
--- Rationale ---
This check detects line segments which are nearly, but not quite, exactly
horizontal or vertical. Sometimes such lines are created by design, but often
they are indicative of a design error.
This check is disabled for italic styles, which often contain nearly-upright
lines.
  • WARN The following glyphs have semi-vertical/semi-horizontal lines:
  • numbersign (U+0023): L<<193.0,455.0>--<336.0,456.0>>
  • numbersign (U+0023): L<<286.0,311.0>--<415.0,312.0>>
  • numbersign (U+0023): L<<459.0,312.0>--<594.0,313.0>>
  • numbersign (U+0023): L<<588.0,276.0>--<435.0,275.0>>
  • numbersign (U+0023): L<<646.0,420.0>--<528.0,419.0>> and uni20B2 (U+20B2): L<<504.0,222.0>--<297.0,221.0>> [code: found-semi-vertical]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 16 10 115 8 69 0
0% 7% 5% 53% 4% 32% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS
  • DEBUG
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant