Skip to content

Instantly share code, notes, and snippets.

@ciembor

ciembor/antykwa_poltawskiego.json

Created December 12, 2019 11:47
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save ciembor/188f58d71789fa37d8907442ff1964d0 to your computer and use it in GitHub Desktop.
Save ciembor/188f58d71789fa37d8907442ff1964d0 to your computer and use it in GitHub Desktop.
Download ZIP
Report from fontbakery check-googlefonts of Antykwa Półtawskiego font quality.
Raw
antykwa_poltawskiego.json
This file has been truncated, but you can view the full file.
{
"result": {
"FAIL": 466,
"INFO": 218,
"PASS": 1644,
"SKIP": 2658,
"WARN": 323
},
"sections": [
{
"checks": [
{
"description": "Check METADATA.pb parse correctly.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/parses>",
[]
],
"logs": [
{
"message": "Font family at 'antykwa_poltawskiego_ttf' lacks a METADATA.pb file.",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to ensure that the METADATA.pb file is not malformed.\n ",
"result": "SKIP"
},
{
"description": "Font designer field in METADATA.pb must not be 'unknown'.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/unknown_designer>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Multiple values in font designer field in METADATA.pb must be separated by commas.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/designer_values>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n We must use commas instead of forward slashes because the server-side code at the fonts.google.com directory will segment the string on the commas into a list of names and display the first item in the list as the \"principal designer\" while the remaining names are identified as \"contributors\".\n \n See eg https://fonts.google.com/specimen/Rubik\n ",
"result": "SKIP"
},
{
"description": "Does METADATA.pb copyright field contain broken links?",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/broken_links>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Ensure METADATA.pb lists all font binaries.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/undeclared_fonts>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The set of font binaries available must match exactly those declared on the METADATA.pb file.\n\n Also, to avoid confusion, we expect that font files are not placed on subdirectories.\n ",
"result": "SKIP"
},
{
"description": "Check font has a license.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/family/has_license>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: check if fonts field only has unique \"full_name\" values.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/unique_full_name_values>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: check if fonts field only contains unique style:weight pairs.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/unique_weight_style_pairs>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb license is \"APACHE2\", \"UFL\" or \"OFL\"?",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/license>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb should contain at least \"menu\" and \"latin\" subsets.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/menu_and_latin>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb subsets should be alphabetically ordered.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/subsets_order>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice is the same in all fonts?",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check that METADATA.pb family values are all the same.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/familyname>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: According Google Fonts standards, families should have a Regular style.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/has_regular>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Regular should be 400.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/regular_is_400>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, has_regular_style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font filenames match font.filename entries?",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/filenames>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "All tabular figures must have the same width across the RIBBI-family.",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/family/tnum_horizontal_metrics>",
[]
],
"logs": [
{
"message": "Unfulfilled Conditions: RIBBI_ttFonts",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Tabular figures need to have the same metrics in all styles in order to allow tables to be set with proper typographic control, but to maintain the placement of decimals and numeric columns between rows.\n\n Here's a good explanation of this:\n https://www.typography.com/techniques/fonts-for-financials/#tabular-figs\n ",
"result": "SKIP"
},
{
"description": "Does font file include unacceptable control character glyphs?",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/family/control_chars>",
[]
],
"logs": [
{
"message": "Unacceptable control characters were not identified.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Use of some unacceptable control characters in the U+0000 - U+001F range can lead to rendering issues on some platforms.\n \n Acceptable control characters are defined as .null (U+0000) and CR (U+000D) for this test.\n ",
"result": "PASS"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpolt-bolditalic.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass expected value for '' is 400 but this font has 700.\n GlyphsApp users should set a Custom Parameter for 'Axis Location' in each master to ensure that the information is accurately built into variable fonts. [code: bad-value]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf |\n|:--- | ---:|\n| Dehinted Size | 186.2kb |\n| Hinted Size | 186.1kb |\n| Increase | -32 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Bold Italic\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Bold Italic\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpolt-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
0
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpolt-bold.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass expected value for '' is 400 but this font has 700.\n GlyphsApp users should set a Custom Parameter for 'Axis Location' in each master to ensure that the information is accurately built into variable fonts. [code: bad-value]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpolt-bold.ttf |\n|:--- | ---:|\n| Dehinted Size | 171.4kb |\n| Hinted Size | 171.4kb |\n| Increase | -32 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Bold\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Bold\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpolt-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
1
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltcond-bolditalic.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass expected value for '' is 400 but this font has 700.\n GlyphsApp users should set a Custom Parameter for 'Axis Location' in each master to ensure that the information is accurately built into variable fonts. [code: bad-value]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf |\n|:--- | ---:|\n| Dehinted Size | 187.3kb |\n| Hinted Size | 187.3kb |\n| Increase | -28 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Bold Italic\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Bold Italic\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
2
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltcond-bold.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass expected value for '' is 400 but this font has 700.\n GlyphsApp users should set a Custom Parameter for 'Axis Location' in each master to ensure that the information is accurately built into variable fonts. [code: bad-value]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltcond-bold.ttf |\n|:--- | ---:|\n| Dehinted Size | 171.9kb |\n| Hinted Size | 171.9kb |\n| Increase | -32 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Bold\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Bold\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
3
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltcond-italic.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass value looks good!",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltcond-italic.ttf |\n|:--- | ---:|\n| Dehinted Size | 185.4kb |\n| Hinted Size | 185.4kb |\n| Increase | -28 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Italic\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Italic\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
4
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltcond-regular.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass value looks good!",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltcond-regular.ttf |\n|:--- | ---:|\n| Dehinted Size | 169.8kb |\n| Hinted Size | 169.8kb |\n| Increase | -28 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Regular\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltcond-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
5
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass expected value for '' is 400 but this font has 700.\n GlyphsApp users should set a Custom Parameter for 'Axis Location' in each master to ensure that the information is accurately built into variable fonts. [code: bad-value]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf |\n|:--- | ---:|\n| Dehinted Size | 186.5kb |\n| Hinted Size | 186.5kb |\n| Increase | -28 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Bold Italic\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Bold Italic\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bolditalic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
6
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltexpd-bold.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass expected value for '' is 400 but this font has 700.\n GlyphsApp users should set a Custom Parameter for 'Axis Location' in each master to ensure that the information is accurately built into variable fonts. [code: bad-value]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf |\n|:--- | ---:|\n| Dehinted Size | 171.2kb |\n| Hinted Size | 171.1kb |\n| Increase | -32 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Bold\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Bold\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-bold.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
7
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltexpd-italic.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass value looks good!",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf |\n|:--- | ---:|\n| Dehinted Size | 186.9kb |\n| Hinted Size | 186.9kb |\n| Increase | -28 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/unitsperem_strict>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Even though unitsPerEm (1000) in this font is reasonable. It is strongly advised to consider changing it to 2000, since it will likely improve the quality of Variable Fonts by avoiding excessive rounding of coordinates on interpolations. [code: legacy-value]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n Even though the OpenType spec allows unitsPerEm to be any value between 16 and 16384, the Google Fonts project aims at a narrower set of reasonable values.\n\n The spec suggests usage of powers of two in order to get some performance improvements on legacy renderers, so those values are acceptable.\n\n But value of 500 or 1000 are also acceptable, with the added benefit that it makes upm math easier for designers, while the performance hit of not using a power of two is most likely negligible nowadays.\n\n Another acceptable value is 2000. Since TT outlines are all integers (no floats), then instances in a VF suffer rounding compromises, and therefore a 1000 UPM is to small because it forces too many such compromises.\n \n Therefore 2000 is a good 'new VF standard', because 2000 is a simple 2x conversion from existing fonts drawn on a 1000 UPM, and anyone who knows what 10 units can do for 1000 UPM will know what 20 units does too.\n\n Additionally, values above 2048 would result in filesize increases with not much added benefit.\n ",
"result": "WARN"
},
{
"description": "Version number has increased since previous release on Google Fonts?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/version_bump>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont, github_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Glyphs are similiar to Google Fonts version?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/production_glyphs_similarity>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: api_gfonts_ttFont",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsSelection value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fsselection>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking post.italicAngle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/italic_angle>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The 'post' table italicAngle property should be a reasonable amount, likely not more than -20\u00b0, never more than -30\u00b0, and never greater than 0\u00b0. Note that in the OpenType specification, the value is negative for a lean rightwards.\n\n https://docs.microsoft.com/en-us/typography/opentype/spec/post\n ",
"result": "SKIP"
},
{
"description": "Checking head.macStyle value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/mac_style>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The values of the flags on the macStyle entry on the 'head' OpenType table that describe whether a font is bold and/or italic must be coherent with the actual style of the font as inferred by its filename.\n ",
"result": "SKIP"
},
{
"description": "Check if each glyph has the recommended amount of contours.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/contour_count>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "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.\n\nThe following glyphs do not have the recommended number of contours:\n\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: asterisk.math\tContours detected: 6\tExpected: 1\nGlyph name: interrobang\tContours detected: 3\tExpected: 2\nGlyph name: uni03D6\tContours detected: 1\tExpected: 2\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: baht\tContours detected: 5\tExpected: 3\nGlyph name: divorced\tContours detected: 5\tExpected: 3\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ydotbelow\tContours detected: 3\tExpected: 2\nGlyph name: yhookabove\tContours detected: 3\tExpected: 2\nGlyph name: ytilde\tContours detected: 3\tExpected: 2\nGlyph name: ygrave\tContours detected: 3\tExpected: 2\nGlyph name: ycircumflex\tContours detected: 3\tExpected: 2\nGlyph name: ydieresis\tContours detected: 4\tExpected: 3\nGlyph name: yacute\tContours detected: 3\tExpected: 2\nGlyph name: daggerdbl\tContours detected: 7\tExpected: 1 or 3\nGlyph name: y\tContours detected: 2\tExpected: 1\nGlyph name: asterisk\tContours detected: 6\tExpected: 1 or 4\nGlyph name: lira\tContours detected: 2\tExpected: 1\nGlyph name: colonmonetary\tContours detected: 2\tExpected: 1 or 3\nGlyph name: dagger\tContours detected: 4\tExpected: 1 or 2 [code: contour-count]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n\n However, a quotedbl should have 2 contours, unless the font belongs to a display family.\n\n 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.\n ",
"result": "WARN"
},
{
"description": "Copyright field for this font on METADATA.pb matches all copyright notice entries on the name table ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/copyright>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has all mandatory 'name' table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/mandatory_entries>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: FONT_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Checks that the family name infered from the font filename matches the string at nameID 1 (NAMEID_FONT_FAMILY_NAME) if it conforms to RIBBI and otherwise checks that nameID 1 is the family name + the style name.\n ",
"result": "SKIP"
},
{
"description": "Check name table: FONT_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/subfamilyname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "SUBFAMILY_NAME for Mac \"Italic\" must be \"\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
},
{
"message": "SUBFAMILY_NAME for Win \"Italic\" must be \"Regular\" [code: bad-familyname]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Check name table: FULL_FONT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/fullfontname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style_with_spaces",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: POSTSCRIPT_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/postscriptname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_FAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicfamilyname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/typographicsubfamilyname>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "TYPOGRAPHIC_SUBFAMILY_NAME entries are all good.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Length of copyright notice must not exceed 500 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/copyright_length>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "All copyright notice name entries on the 'name' table are shorter than 500 characters.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n This is an arbitrary max length for the copyright notice field of the name table. We simply don't want such notices to be too long. Typically such notices are actually much shorter than this with a length of roughly 70 or 80 characters.\n ",
"result": "PASS"
},
{
"description": "Familyname must be unique according to namecheck.fontdata.com",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontdata_namecheck>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Font familyname seems to be unique.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n We need to check names are not already used, and today the best place to check that is http://namecheck.fontdata.com\n ",
"result": "PASS"
},
{
"description": "Check for font-v versioning.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fontv>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Version string is: \"Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853\"\nThe version string must ideally include a git commit hash and either a \"dev\" or a \"release\" suffix such as in the example below:\n\"Version 1.3; git-0d08353-release\" [code: bad-format]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The git sha1 tagging and dev/release features of Source Foundry `font-v` tool are awesome and we would love to consider upstreaming the approach into fontmake someday. For now we only emit a WARN if a given font does not yet follow the experimental versioning style, but at some point we may start enforcing it.\n ",
"result": "INFO"
},
{
"description": "Check a static ttf can be generated from a variable font.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/generate_static>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Google Fonts may serve static fonts which have been generated from variable fonts. This test will attempt to generate a static ttf using fontTool's varLib mutator.\n\n The target font will be the mean of each axis e.g:\n\n **VF font axes**\n\n - min weight, max weight = 400, 800\n - min width, max width = 50, 100\n\n **Target Instance**\n\n - weight = 600\n - width = 75\n ",
"result": "SKIP"
},
{
"description": "Check that variable fonts have an HVAR table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont/has_HVAR>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Not having a HVAR table can lead to costly text-layout operations on some platforms, which we want to avoid.\n\n So, all variable fonts on the Google Fonts collection should have an HVAR with valid values.\n\n More info on the HVAR table can be found at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/otvaroverview#variation-data-tables-and-miscellaneous-requirements\n ",
"result": "SKIP"
},
{
"description": "Font enables smart dropout control in \"prep\" table instructions?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/smart_dropout>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n This setup is meant to ensure consistent rendering quality for fonts across all devices (with different rendering/hinting capabilities).\n\n Below is the snippet of instructions we expect to see in the fonts:\n B8 01 FF PUSHW 0x01FF\n 85 SCANCTRL (unconditinally turn on\n dropout control mode)\n B0 04 PUSHB 0x04\n 8D SCANTYPE (enable smart dropout control)\n\n \"Smart dropout control\" means activating rules 1, 2 and 5:\n Rule 1: If a pixel's center falls within the glyph outline,\n that pixel is turned on.\n Rule 2: If a contour falls exactly on a pixel's center,\n that pixel is turned on.\n Rule 5: If a scan line between two adjacent pixel centers\n (either vertical or horizontal) is intersected\n by both an on-Transition contour and an off-Transition\n contour and neither of the pixels was already turned on\n by rules 1 and 2, turn on the pixel which is closer to\n the midpoint between the on-Transition contour and\n off-Transition contour. This is \"Smart\" dropout control.\n\n For more detailed info (such as other rules not enabled in this snippet), please refer to the TrueType Instruction Set documentation.\n ",
"result": "FAIL"
},
{
"description": "There must not be VTT Talk sources in the font.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vttclean>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "There are no tables with VTT Talk sources embedded in the font.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The goal here is to reduce filesizes and improve pageloading when dealing with webfonts.\n\n The VTT Talk sources are not necessary at runtime and endup being just dead weight when left embedded in the font binaries. The sources should be kept on the project files but stripped out when building release binaries.\n ",
"result": "PASS"
},
{
"description": "Are there unwanted Apple tables?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/aat>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "There are no unwanted AAT tables.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Apple's TrueType reference manual [1] describes SFNT tables not in the Microsoft OpenType specification [2] and these can sometimes sneak into final release files, but Google Fonts should only have OpenType tables.\n\n [1] https://developer.apple.com/fonts/TrueType-Reference-Manual/RM06/Chap6.html\n [2] https://docs.microsoft.com/en-us/typography/opentype/spec/\n ",
"result": "PASS"
},
{
"description": "All name entries referenced by fvar instances exist on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fvar_name_entries>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The purpose of this check is to make sure that all name entries referenced by variable font instances do exist in the name table.\n ",
"result": "SKIP"
},
{
"description": "A variable font must have named instances.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_has_instances>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Named instances must be present in all variable fonts in order not to frustrate the users' typical expectations of a traditional static font workflow.\n ",
"result": "SKIP"
},
{
"description": "Variable font weight coordinates must be multiples of 100.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_weight_instances>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The named instances on the weight axis of a variable font must have coordinates that are multiples of 100 on the design space.\n ",
"result": "SKIP"
},
{
"description": "PPEM must be an integer on hinted fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/integer_ppem_if_hinted>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_hinted",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Hinted fonts must have head table flag bit 3 set.\n\n Per https://docs.microsoft.com/en-us/typography/opentype/spec/head, bit 3 of Head::flags decides whether PPEM should be rounded. This bit should always be set for hinted fonts.\n\n Note:\n Bit 3 = Force ppem to integer values for all internal scaler math;\n May use fractional ppem sizes if this bit is clear;\n ",
"result": "SKIP"
},
{
"description": "Are there caret positions declared for every ligature?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/ligature_carets>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n ",
"result": "WARN"
},
{
"description": "Is there kerning info for non-ligated sequences?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/kerning_for_non_ligated_sequences>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "GPOS table lacks kerning info for the following non-ligated sequences:\n\t- f + i\n\t- i + k\n\t- f_f + i\n\t- I + J\n\t- i + j\n\n [code: lacks-kern-info]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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).\n ",
"result": "WARN"
},
{
"description": "Combined length of family and style must not exceed 27 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/family_and_style_max_length>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "All name entries are good.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n According to a GlyphsApp tutorial [1], in order to make sure all versions of Windows recognize it as a valid font file, we must make sure that the concatenated length of the familyname (NameID.FONT_FAMILY_NAME) and style (NameID.FONT_SUBFAMILY_NAME) strings in the name table do not exceed 20 characters.\n\n After discussing the problem in more detail at `FontBakery issue #2179 [2] we decided that allowing up to 27 chars would still be on the safe side, though.\n\n [1] https://glyphsapp.com/tutorials/multiple-masters-part-3-setting-up-instances\n [2] https://github.com/googlefonts/fontbakery/issues/2179\n ",
"result": "PASS"
},
{
"description": "Directory name in GFonts repo structure must match NameID 1 of the regular.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/repo/dirname_matches_nameid_1>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: gfonts_repo_structure",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check if the vertical metrics of a family are similar to the same family hosted on Google Fonts.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vertical_metrics_regressions>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: remote_styles",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n If the family already exists on Google Fonts, we need to ensure that the checked family's vertical metrics are similar. This check will test the following schema which was outlined in Fontbakery issue #1162 [1]:\n\n - The family should visually have the same vertical metrics as the\n Regular style hosted on Google Fonts.\n - If the family on Google Fonts has differing hhea and typo metrics,\n the family being checked should use the typo metrics for both the\n hhea and typo entries.\n - If the family on Google Fonts has use typo metrics not enabled and the\n family being checked has it enabled, the hhea and typo metrics\n should use the family on Google Fonts winAscent and winDescent values.\n - If the upms differ, the values must be scaled so the visual appearance\n is the same.\n\n [1] https://github.com/googlefonts/fontbakery/issues/1162\n ",
"result": "SKIP"
},
{
"description": "Check variable font instances have correct coordinate values",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_coordinates>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Check variable font instances have correct names",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-italic.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/varfont_instance_names>",
[
[
"font",
8
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking file is named canonically.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/canonical_filename>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Style name used in \"antykwa_poltawskiego_ttf/antpoltexpd-regular.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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n A font's filename must be composed in the following manner:\n <familyname>-<stylename>.ttf\n\n - Nunito-Regular.ttf,\n - Oswald-BoldItalic.ttf\n\n Variable fonts must list the axis tags in alphabetical order in square brackets and separated by commas:\n \n - Roboto[wdth,wght].ttf\n - Familyname-Italic[wght].ttf\n ",
"result": "FAIL"
},
{
"description": "Does DESCRIPTION file contain broken links?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/broken_links>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The snippet of HTML in the DESCRIPTION.en_us.html file is added to the font family webpage on the Google Fonts website. For that reason, all hyperlinks in it must be properly working. \n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file contain a upstream Git repo URL?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/git_url>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n The contents of the DESCRIPTION.en-us.html file are displayed on the Google Fonts website in the about section of each font family specimen page.\n\n Since all of the Google Fonts collection is composed of libre-licensed fonts, this check enforces a policy that there must be a hypertext link in that page directing users to the repository where the font project files are made available.\n\n Such hosting is typically done on sites like Github, Gitlab, GNU Savannah or any other git-based version control service.\n ",
"result": "SKIP"
},
{
"description": "Does DESCRIPTION file mention when a family is available as variable font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/variable_font>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: is_variable_font, description",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n Families with variable fonts do not always mention that in their descriptions. Therefore, this check ensures that a standard boilerplate sentence is present in the DESCRIPTION.en_us.html files for all those families which are available as variable fonts.\n ",
"result": "SKIP"
},
{
"description": "Is this a proper HTML snippet?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/valid_html>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: descfile",
"status": "SKIP",
"traceback": null
}
],
"rationale": "\n When packaging families for being pushed to the `google/fonts` git repo, if there is no DESCRIPTION.en_us.html file, some older versions of the `add_font.py` tool insert a dummy description file which contains invalid html.\n\n This file needs to either be replaced with an existing description file or edited by hand.\n ",
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have more than 200 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/min_length>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "DESCRIPTION.en_us.html must have less than 1000 bytes.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/description/max_length>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: description",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 fsType does not impose restrictions.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/fstype>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "In this font fsType is set to 12 meaning that:\nThe font may be embedded, and temporarily loaded on the remote system, but documents that use it must not be editable.The font may be embedded but must only be installed temporarily on other systems.\n\nNo 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]",
"status": "FAIL",
"traceback": null
}
],
"rationale": "\n 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.\n\n More detailed info is available at:\n https://docs.microsoft.com/en-us/typography/opentype/spec/os2#fstype\n ",
"result": "FAIL"
},
{
"description": "Checking OS/2 achVendID.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/vendor_id>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "OS/2 VendorID is 'UKWN', a font editor default. You should set it to your own 4 character code, and register that code with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: bad]",
"status": "WARN",
"traceback": null
}
],
"result": "WARN"
},
{
"description": "Check `Google Fonts Latin Core` glyph coverage.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/glyph_coverage>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "OK",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.\n ",
"result": "PASS"
},
{
"description": "Substitute copyright, registered and trademark symbols in name table entries.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/unwanted_chars>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "No need to substitute copyright, registered and trademark symbols in name table entries of this font.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Checking OS/2 usWeightClass.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/usweightclass>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "OS/2 usWeightClass value looks good!",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Check copyright namerecords match license file.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: license",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "License URL matches License text on name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/license_url>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry. Currently accepted licenses are Apache: 'http://www.apache.org/licenses/LICENSE-2.0' or Open Font License: 'http://scripts.sil.org/OFL'\nFor a small set of legacy families the Ubuntu Font License 'https://www.ubuntu.com/legal/terms-and-policies/font-licence' may be acceptable as well.\nWhen in doubt, please choose OFL for new font projects. [code: no-license-found]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Description strings in the name table must not exceed 200 characters.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/description_max_length>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "All description name records have reasonably small lengths.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries.\n\n In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars.\n\n Longer strings are likely instances of the FontLab bug.\n ",
"result": "PASS"
},
{
"description": "Show hinting filesize impact.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/hinting_impact>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Hinting filesize impact:\n\n| | antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf |\n|:--- | ---:|\n| Dehinted Size | 170.6kb |\n| Hinted Size | 170.6kb |\n| Increase | -28 bytes |\n| Change | -0.0 % |\n [code: size-impact]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check is merely informative, displaying and useful comparison of filesizes after ttfautohint usage versus unhinted font files.\n ",
"result": "INFO"
},
{
"description": "Version format is correct in 'name' table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/version_format>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Version format in NAME table entries is correct.",
"status": "PASS",
"traceback": null
}
],
"result": "PASS"
},
{
"description": "Font has ttfautohint params?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/has_ttfautohint_params>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
},
{
"message": "Font appears to our heuristic as not hinted using ttfautohint. [code: not-hinted]",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Font has old ttfautohint applied?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/old_ttfautohint>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853', 'Version 1.101;PS 1.101;hotconv 1.0.49;makeotf.lib2.0.14853'] [code: version-not-detected]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n This check finds which version of ttfautohint was used, by inspecting name table entries and then finds which version of ttfautohint is currently installed in the system.\n ",
"result": "INFO"
},
{
"description": "EPAR table present in font?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/epar>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "EPAR table not present in font. To learn more see https://github.com/googlefonts/fontbakery/issues/818 [code: lacks-EPAR]",
"status": "INFO",
"traceback": null
}
],
"rationale": "\n The EPAR table is/was a way of expressing common licensing permissions and restrictions in metadata; while almost nothing supported it, Dave Crossland wonders that adding it to everything in Google Fonts could help make it more popular.\n\n More info is available at:\n https://davelab6.github.io/epar/\n ",
"result": "INFO"
},
{
"description": "Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/gasp>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "These are the ppm ranges declared on the gasp table:\n\nPPM <= 65535:\n\tflag = 0x02\n\t- Use grayscale rendering\n [code: ranges]",
"status": "INFO",
"traceback": null
},
{
"message": "The gasp range 0xFFFF value 0x02 should be set to 0x0F. [code: unset-flags]",
"status": "WARN",
"traceback": null
}
],
"rationale": "\n 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.\n \n In this scenario it makes sense to simply toggle all 4 flags ON for all font sizes.\n ",
"result": "WARN"
},
{
"description": "Make sure family name does not begin with a digit.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/familyname_first_char>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Font family name first character is not a digit.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n Font family names which start with a numeral are often not discoverable in Windows applications.\n ",
"result": "PASS"
},
{
"description": "Are there non-ASCII characters in ASCII-only NAME table entries?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/name/ascii_only_entries>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "None of the ASCII-only NAME table entries contain non-ASCII characteres.",
"status": "PASS",
"traceback": null
}
],
"rationale": "\n The OpenType spec requires ASCII for the POSTSCRIPT_NAME (nameID 6).\n \n For COPYRIGHT_NOTICE (nameID 0) ASCII is required because that string should be the same in CFF fonts which also have this requirement in the OpenType spec.\n\n Note:\n A common place where we find non-ASCII strings is on name table entries with NameID > 18, which are expressly for localising the ASCII-only IDs into Hindi / Arabic / etc.\n ",
"result": "PASS"
},
{
"description": "METADATA.pb: Fontfamily is listed on Google Fonts API?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/listed_on_gfonts>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.name field matches family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_name>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checks METADATA.pb font.post_script_name matches postscript name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/post_script_name>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name value matches fullname declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/full_name>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name value should be same as the family name declared on the name table.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/font_name>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata, style",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name and font.post_script_name fields have equivalent values ?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_fullname_postscript>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename and font.post_script_name fields have equivalent values?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_filename_postscript>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_name_values>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.full_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_full_name_values>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.filename field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_filename_values>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: style, family_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.post_script_name field contains font name in right format?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_post_script_name_values>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in METADATA.pb",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/valid_copyright>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Copyright notices match canonical pattern in fonts",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/font_copyright>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
},
{
"message": "Name Table entry: Copyright notices should match a pattern similar to: \"Copyright 2019 The Familyname Project Authors (git url)\"\nBut instead we have got:\n\"Copyright 2003, 2009 B. Jackowski and J. M. Nowacki (on behalf of TeX users groups). This work is released under the GUST Font License -- see http://tug.org/fonts/licenses/GUST-FONT-LICENSE.txt for details.\" [code: bad-notice-format]",
"status": "FAIL",
"traceback": null
}
],
"result": "FAIL"
},
{
"description": "Copyright notice on METADATA.pb should not contain 'Reserved Font Name'.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/reserved_font_name>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Copyright notice shouldn't exceed 500 chars.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/copyright_max_length>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"italic\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/italic_style>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.style \"normal\" matches font internals?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/normal_style>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb font.name and font.full_name fields match the values declared on the name table?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/nameid/family_and_full_names>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check if fontname is not camel cased.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/fontname_not_camel_cased>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check font name is the same as family name.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_name_familyname>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: family_metadata, font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Check that font weight has a canonical value.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_weight_value>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Checking OS/2 usWeightClass matches weight specified at METADATA.pb.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/os2_weightclass>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb weight matches postScriptName.",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/match_weight_postscript>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "METADATA.pb: Font styles are named canonically?",
"filename": "antykwa_poltawskiego_ttf/antpoltexpd-regular.ttf",
"key": [
"<Section: Google Fonts>",
"<FontBakeryCheck:com.google.fonts/check/metadata/canonical_style_names>",
[
[
"font",
9
]
]
],
"logs": [
{
"message": "Unfulfilled Conditions: font_metadata",
"status": "SKIP",
"traceback": null
}
],
"result": "SKIP"
},
{
"description": "Stricter unitsPerEm criteria for Google Fonts. ",
"filename": "a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment