Sixtyfour: Version 2.000;gftools[0.9.33] added

[vv-monsalve]

d82ab2b: [gftools-packager] Sixtyfour: Version 2.000;gftools[0.9.33] added

• Sixtyfour Version 2.000;gftools[0.9.33] taken from the upstream repo https://github.com/jenskutilek/homecomputer-fonts at commit jenskutilek/homecomputer-fonts@9b182d8.

[vv-monsalve]

• 🔥 FAIL: Does DESCRIPTION file contain broken links?

The link will exist when #6917 is merged. We should remember to counter-check the link once in prod.

• 🔥 FAIL: METADATA.pb: Check URL on copyright string is the same as in repository_url field.

I've inspected the links in METADATA and DESCRIPTION files, and they both use https://github.com/jenskutilek/homecomputer-fonts. So not clear why is this Fail reported.

• 🔥 FAIL: Check Google Fonts glyph coverage.
• 🔥 FAIL: Check font follows the Google Fonts vertical metric schema

Due to the historic origin of the fonts it was agreed to accept these fails.

• 🔥 FAIL: Check variable font instances

Given the font only includes custom axes it is accepted for them to include custom named instances. After Kablammo's case this was confirmed for the homecomputer fonts. I need to include this to the GF-Guide

• 🔥 FAIL: Check a font's STAT table contains compulsory Axis Values.

Bug reported in googlefonts/axisregistry#99 (comment)

• 🔥 FAIL: Validate METADATA.pb axes tags are defined in gf_axisregistry.

The SCAN and BLED axes were already merged in the googlefonts/axisregistry repo and will be brought with an upcoming git subtree pull. Please only merge this PR once I create that git subtree pull. I'll inform you about it

• ⚠ WARN: METADATA.pb: Designers are listed correctly on the Google Fonts catalog?

Waiting for the designer's info to add his entry to the catalog.

[vv-monsalve]

Updated

Sixtyfour: Version 2.000 added

---

64e7c16: [gftools-packager] Sixtyfour: Version 2.000 added

• Sixtyfour Version 2.000 taken from the upstream repo https://github.com/jenskutilek/homecomputer-fonts at commit jenskutilek/homecomputer-fonts@9a28003.

[vv-monsalve]

Designer Jens Kutílek was added in #6935

[github-actions]

FontBakery report

fontbakery version: 0.10.3

[1] Experimental checks

🔥 FAIL: Shapes languages in all GF glyphsets. (com.google.fonts/check/glyphsets/shape_languages)

• 🔥 FAIL GF_Latin_Kernel/kl_Latn (Kalaallisut): [FAIL: Some mark glyphs were missing: ◌̀, ◌́, ◌̂, ◌̃, ◌̊] [code: failed-language-shaping]
• 🔥 FAIL GF_Latin_Kernel/zu_Latn (Zulu): [FAIL: Some mark glyphs were missing: ◌̀, ◌́, ◌̂, ◌̃, ◌̄, ◌̆, ◌̈, ◌̊, ◌̧] [code: failed-language-shaping]

[1] Family checks

ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

• ℹ INFO From a total of 1 font files, 0 of them (0.00%) lack a STAT table.

  And these are the most common STAT axis orderings:
  ('SCAN-BLED', 1) [code: summary]

[17] Sixtyfour[BLED,SCAN].ttf

🔥 FAIL: Does DESCRIPTION file contain broken links? (com.google.fonts/check/description/broken_links)

• 🔥 FAIL The following links are broken in the DESCRIPTION file:
  https://fonts.google.com/specimen/Workbench (status code: 404) [code: broken-links]

🔥 FAIL: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)

• 🔥 FAIL Missing required codepoints:

  • 0x0308 (COMBINING DIAERESIS)

  • 0x0300 (COMBINING GRAVE ACCENT)

  • 0x0301 (COMBINING ACUTE ACCENT)

  • 0x030B (COMBINING DOUBLE ACUTE ACCENT)

  • 0x0304 (COMBINING MACRON)

  • 0x0102 (LATIN CAPITAL LETTER A WITH BREVE)

  • 0x0100 (LATIN CAPITAL LETTER A WITH MACRON)

  • 0x0104 (LATIN CAPITAL LETTER A WITH OGONEK)

  • 0x0106 (LATIN CAPITAL LETTER C WITH ACUTE)

  • 0x010C (LATIN CAPITAL LETTER C WITH CARON)

  • 117 more.

Use -F or --full-lists to disable shortening of long lists. [code: missing-codepoints]

🔥 FAIL: Check a font's STAT table contains compulsory Axis Values. (com.google.fonts/check/STAT)

• 🔥 FAIL Compulsory STAT Axis Values are incorrect:

Name	Axis	Current Value	Current Flags	Current LinkedValue	Expected Value	Expected Flags	Expected LinkedValue
Regular	wght	N/A	N/A	N/A	400.0	0	700.0
[code: bad-axis-values]

🔥 FAIL: Check variable font instances (com.google.fonts/check/fvar_instances)

• 🔥 FAIL fvar instances are incorrect:

• Delete additional instances

Name	current	expected
Slight	SCAN=-45.0, BLED=0.0	N/A
Delicate	SCAN=-53.0, BLED=0.0	N/A
Evenly	SCAN=-27.0, BLED=0.0	N/A
Overlapping	SCAN=37.0, BLED=0.0	N/A
Maximum	SCAN=100.0, BLED=0.0	N/A
Overexposed	SCAN=67.0, BLED=0.0	N/A
Touching	SCAN=21.0, BLED=0.0	N/A
Regular	SCAN=0.0, BLED=0.0	SCAN=0.0, BLED=0.0

🔥 FAIL: Check font follows the Google Fonts vertical metric schema (com.google.fonts/check/vertical_metrics)

• 🔥 FAIL The sum of hhea.ascender + abs(hhea.descender) + hhea.lineGap is 1024 when it should be at least 1228 [code: bad-hhea-range]

🔥 FAIL: Validate METADATA.pb axes tags are defined in gf_axisregistry. (com.google.fonts/check/metadata/gf_axisregistry_valid_tags)

• 🔥 FAIL The font variation axis 'BLED' is not yet registered on Google Fonts Axis Registry. [code: bad-axis-tag]
• 🔥 FAIL The font variation axis 'SCAN' is not yet registered on Google Fonts Axis Registry. [code: bad-axis-tag]

⚠ WARN: Check for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)

• ⚠ WARN The following codepoints supported by the font are not covered by
  any subsets defined in the font's metadata file, and will never
  be served. You can solve this by either manually adding additional
  subset declarations to METADATA.pb, or by editing the glyphset
  definitions.

• U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi

• U+2021 DOUBLE DAGGER: try adding adlam

• U+2030 PER MILLE SIGN: try adding adlam

• U+2126 OHM SIGN: not included in any glyphset definition

• U+2501 BOX DRAWINGS HEAVY HORIZONTAL: not included in any glyphset definition

• U+2503 BOX DRAWINGS HEAVY VERTICAL: not included in any glyphset definition

• U+250F BOX DRAWINGS HEAVY DOWN AND RIGHT: not included in any glyphset definition

• U+2513 BOX DRAWINGS HEAVY DOWN AND LEFT: not included in any glyphset definition

• U+2517 BOX DRAWINGS HEAVY UP AND RIGHT: not included in any glyphset definition

• U+251B BOX DRAWINGS HEAVY UP AND LEFT: not included in any glyphset definition
  200 more.

Use -F or --full-lists to disable shortening of long lists.

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, math, menu, symbols [code: unreachable-subsetting]

⚠ WARN: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)

• ⚠ WARN It seems that Jens Kutílek is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]

ℹ INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)

• ℹ INFO Found a git repo URL: https://github.com/jenskutilek/homecomputer-fonts [code: url-found]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

• ℹ INFO Hinting filesize impact:

	ofl/sixtyfour/Sixtyfour[BLED,SCAN].ttf
Dehinted Size	69.9kb
Hinted Size	69.9kb
Increase	24 bytes
Change	0.0 %
[code: size-impact]

ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)

• ℹ INFO 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 2.000'] [code: version-not-detected]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

• ℹ INFO EPAR table not present in font. To learn more see When missing EPAR table, just emit INFO alert fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

• ℹ INFO These are the ppm ranges declared on the gasp table:

PPM <= 65535:
flag = 0x0F
- Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
- Use smoothing along multiple axes with ClearType®
[code: ranges]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

• ℹ INFO Version string is: "Version 2.000"
  The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
  "Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

• ℹ INFO Latn [code: dlng-tag]
• ℹ INFO Latn [code: slng-tag]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

• ℹ INFO This font contains the following optional tables:

  • loca

  • prep

  • GSUB

  • gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

• ℹ INFO ofl/sixtyfour [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	7	2	55	10	181	0
0%	3%	1%	22%	4%	71%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[github-actions]

FontBakery report

fontbakery version: 0.10.3

[1] Experimental checks

🔥 FAIL: Shapes languages in all GF glyphsets. (com.google.fonts/check/glyphsets/shape_languages)

• 🔥 FAIL GF_Latin_Kernel/kl_Latn (Kalaallisut): [FAIL: Some mark glyphs were missing: ◌̀, ◌́, ◌̂, ◌̃, ◌̊] [code: failed-language-shaping]
• 🔥 FAIL GF_Latin_Kernel/zu_Latn (Zulu): [FAIL: Some mark glyphs were missing: ◌̀, ◌́, ◌̂, ◌̃, ◌̄, ◌̆, ◌̈, ◌̊, ◌̧] [code: failed-language-shaping]

[1] Family checks

ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

• ℹ INFO From a total of 1 font files, 0 of them (0.00%) lack a STAT table.

  And these are the most common STAT axis orderings:
  ('SCAN-BLED', 1) [code: summary]

[17] Sixtyfour[BLED,SCAN].ttf

🔥 FAIL: Does DESCRIPTION file contain broken links? (com.google.fonts/check/description/broken_links)

• 🔥 FAIL The following links are broken in the DESCRIPTION file:
  https://fonts.google.com/specimen/Workbench (status code: 404) [code: broken-links]

🔥 FAIL: Check Google Fonts glyph coverage. (com.google.fonts/check/glyph_coverage)

• 🔥 FAIL Missing required codepoints:

  • 0x0308 (COMBINING DIAERESIS)

  • 0x0300 (COMBINING GRAVE ACCENT)

  • 0x0301 (COMBINING ACUTE ACCENT)

  • 0x030B (COMBINING DOUBLE ACUTE ACCENT)

  • 0x0304 (COMBINING MACRON)

  • 0x0102 (LATIN CAPITAL LETTER A WITH BREVE)

  • 0x0100 (LATIN CAPITAL LETTER A WITH MACRON)

  • 0x0104 (LATIN CAPITAL LETTER A WITH OGONEK)

  • 0x0106 (LATIN CAPITAL LETTER C WITH ACUTE)

  • 0x010C (LATIN CAPITAL LETTER C WITH CARON)

  • 117 more.

Use -F or --full-lists to disable shortening of long lists. [code: missing-codepoints]

🔥 FAIL: Check a font's STAT table contains compulsory Axis Values. (com.google.fonts/check/STAT)

• 🔥 FAIL Compulsory STAT Axis Values are incorrect:

Name	Axis	Current Value	Current Flags	Current LinkedValue	Expected Value	Expected Flags	Expected LinkedValue
Regular	wght	N/A	N/A	N/A	400.0	0	700.0
[code: bad-axis-values]

🔥 FAIL: Check variable font instances (com.google.fonts/check/fvar_instances)

• 🔥 FAIL fvar instances are incorrect:

• Delete additional instances

Name	current	expected
Delicate	SCAN=-53.0, BLED=0.0	N/A
Maximum	SCAN=100.0, BLED=0.0	N/A
Evenly	SCAN=-27.0, BLED=0.0	N/A
Touching	SCAN=21.0, BLED=0.0	N/A
Slight	SCAN=-45.0, BLED=0.0	N/A
Overexposed	SCAN=67.0, BLED=0.0	N/A
Overlapping	SCAN=37.0, BLED=0.0	N/A
Regular	SCAN=0.0, BLED=0.0	SCAN=0.0, BLED=0.0

🔥 FAIL: Check font follows the Google Fonts vertical metric schema (com.google.fonts/check/vertical_metrics)

• 🔥 FAIL The sum of hhea.ascender + abs(hhea.descender) + hhea.lineGap is 1024 when it should be at least 1228 [code: bad-hhea-range]

🔥 FAIL: Validate METADATA.pb axes tags are defined in gf_axisregistry. (com.google.fonts/check/metadata/gf_axisregistry_valid_tags)

• 🔥 FAIL The font variation axis 'BLED' is not yet registered on Google Fonts Axis Registry. [code: bad-axis-tag]
• 🔥 FAIL The font variation axis 'SCAN' is not yet registered on Google Fonts Axis Registry. [code: bad-axis-tag]

⚠ WARN: Check for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)

• ⚠ WARN The following codepoints supported by the font are not covered by
  any subsets defined in the font's metadata file, and will never
  be served. You can solve this by either manually adding additional
  subset declarations to METADATA.pb, or by editing the glyphset
  definitions.

• U+02D9 DOT ABOVE: try adding one of: yi, canadian-aboriginal

• U+2021 DOUBLE DAGGER: try adding adlam

• U+2030 PER MILLE SIGN: try adding adlam

• U+2126 OHM SIGN: not included in any glyphset definition

• U+2501 BOX DRAWINGS HEAVY HORIZONTAL: not included in any glyphset definition

• U+2503 BOX DRAWINGS HEAVY VERTICAL: not included in any glyphset definition

• U+250F BOX DRAWINGS HEAVY DOWN AND RIGHT: not included in any glyphset definition

• U+2513 BOX DRAWINGS HEAVY DOWN AND LEFT: not included in any glyphset definition

• U+2517 BOX DRAWINGS HEAVY UP AND RIGHT: not included in any glyphset definition

• U+251B BOX DRAWINGS HEAVY UP AND LEFT: not included in any glyphset definition
  200 more.

Use -F or --full-lists to disable shortening of long lists.

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, math, menu, symbols [code: unreachable-subsetting]

⚠ WARN: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)

• ⚠ WARN It seems that Jens Kutílek is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]

ℹ INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)

• ℹ INFO Found a git repo URL: https://github.com/jenskutilek/homecomputer-fonts [code: url-found]

ℹ INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)

• ℹ INFO Hinting filesize impact:

	ofl/sixtyfour/Sixtyfour[BLED,SCAN].ttf
Dehinted Size	69.9kb
Hinted Size	69.9kb
Increase	24 bytes
Change	0.0 %
[code: size-impact]

ℹ INFO: Font has old ttfautohint applied? (com.google.fonts/check/old_ttfautohint)

• ℹ INFO 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 2.000'] [code: version-not-detected]

ℹ INFO: EPAR table present in font? (com.google.fonts/check/epar)

• ℹ INFO EPAR table not present in font. To learn more see When missing EPAR table, just emit INFO alert fonttools/fontbakery#818 [code: lacks-EPAR]

ℹ INFO: Is the Grid-fitting and Scan-conversion Procedure ('gasp') table set to optimize rendering? (com.google.fonts/check/gasp)

• ℹ INFO These are the ppm ranges declared on the gasp table:

PPM <= 65535:
flag = 0x0F
- Use grid-fitting
- Use grayscale rendering
- Use gridfitting with ClearType symmetric smoothing
- Use smoothing along multiple axes with ClearType®
[code: ranges]

ℹ INFO: Check for font-v versioning. (com.google.fonts/check/fontv)

• ℹ INFO Version string is: "Version 2.000"
  The version string must ideally include a git commit hash and either a "dev" or a "release" suffix such as in the example below:
  "Version 1.3; git-0d08353-release" [code: bad-format]

ℹ INFO: Ensure fonts have ScriptLangTags declared on the 'meta' table. (com.google.fonts/check/meta/script_lang_tags)

• ℹ INFO Latn [code: dlng-tag]
• ℹ INFO Latn [code: slng-tag]

ℹ INFO: Font contains all required tables? (com.google.fonts/check/required_tables)

• ℹ INFO This font contains the following optional tables:

  • loca

  • prep

  • GSUB

  • gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)

• ℹ INFO ofl/sixtyfour [code: family-path]

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	7	2	55	10	181	0
0%	3%	1%	22%	4%	71%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[RosaWagner]

After discussing the axes with @vv-monsalve, we decided to merge the PR so see how they render in sandbox but she would make a new PR where "Close" is elided in the STAT table for better cross-platform naming consistency.

[vv-monsalve]

Revising the above and taking Kablammo as a benchmark (of a font with only custom axes) I've changed the current Regular fvar table to Close. This way, the fvar matches the STAT table while not making any instance convey the "weight" axis.

I've created a new PR to the upstream repo. Will update this PR once it's merged.