Foldit: Version 1.003 added

[m4rc1e]

2820c7c: [gftools-packager] Foldit: Version 1.003 added

• Foldit Version 1.003 taken from the upstream repo https://github.com/SophiaDesign/Foldit at commit https://github.com/SophiaDesign/Foldit/commit/.

Closes #5093

[gf-bot]

Fontbakery report

Fontbakery version: 0.8.10

[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:
  ('wght', 1) [code: summary]

[17] Foldit[wght].ttf

🔥 FAIL: Validates that when an instance record is included for the default instance, its subfamilyNameID value is set to either 2 or 17 (or something with the same value as 2), and its postScriptNameID value is set to 6 (or something with the same value as 6). (com.adobe.fonts/check/varfont/valid_default_instance_nameids)

• 🔥 FAIL 'Thin' instance has the same coordinates as the default instance; its subfamily name should be 'Regular' [code: invalid-default-instance-subfamily-nameid:257]

⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)

• ⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]

⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API? (com.google.fonts/check/metadata/listed_on_gfonts)

• ⚠ WARN Family not found via Google Fonts API. [code: not-found]

⚠ WARN: Is there kerning info for non-ligated sequences? (com.google.fonts/check/kerning_for_non_ligated_sequences)

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

  • f + f

  • f + i

  • i + f

  • f + l

  • l + f

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

⚠ WARN: A static fonts directory with at least two fonts must accompany variable fonts (com.google.fonts/check/repo/vf_has_static_fonts)

• ⚠ WARN Please consider adding a subdirectory called "static/" and including in it static font files. [code: missing]

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

• ⚠ WARN It seems that Sophia Tai 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]

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

• ⚠ WARN This font file does not have a 'meta' table. [code: lacks-meta-table]

⚠ WARN: Check font contains no unreachable glyphs (com.google.fonts/check/unreachable_glyphs)

• ⚠ WARN The following glyphs could not be reached by codepoint or substitution rules:

  • uni004A0301

  • And uni006A0301
    [code: unreachable-glyphs]

⚠ WARN: Ensure dotted circle glyph is present and can attach marks. (com.google.fonts/check/dotted_circle)

• ⚠ WARN No dotted circle glyph present [code: missing-dotted-circle]

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

• ℹ INFO Hinting filesize impact:

	ofl/foldit/Foldit[wght].ttf
Dehinted Size	508.3kb
Hinted Size	508.3kb
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 1.003'] [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 1.003"
  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: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)

• ℹ INFO No sample_glyphs on METADATA.pb [code: no-samples]

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

• ℹ INFO This font contains the following optional tables:

  • loca

  • prep

  • GPOS

  • GSUB

  • And gasp [code: optional-tables]

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

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

### Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	8	51	9	158	0
0%	0%	4%	22%	4%	70%	0%

Note: The following loglevels were omitted in this report:

• SKIP
• PASS
• DEBUG

[m4rc1e]

Thanks. I'll upload the designers details after lunch in a new pr.

We also need to keep this PR blocked until the latest version of Chrome is out.

[vv-monsalve]

Thanks. I'll upload the designers details after lunch in a new pr.

I've sent an email to the designer so that she can provide an image for her profile. I'll create a PR with her information after that.

[emmamarichal]

@vv-monsalve, sorry I hadn't seen your comment, and I sent a message on instagram to the author. She just added her avatar to the folder. 👌 I can do it if you want, unless you've already started.

[RosaWagner]

@m4rc1e @vv-monsalve writing here what Rod reported in the chat; the font needs to go through the color script again (missing SVG table)

[vv-monsalve]

@vv-monsalve, sorry I hadn't seen your comment, and I sent a message on instagram to the author. She just added her avatar to the folder. 👌 I can do it if you want, unless you've already started.

Ah, ok, she didn't reply to my email so I haven't started it. If she has provided the image now, yes please you could add her bio ingo if that's ok for you. Thanks

[vv-monsalve]

@m4rc1e @vv-monsalve writing here what Rod reported in the chat; the font needs to go through the color script again (missing SVG table)

@m4rc1e Is that something we should do it independently (post-process) or is it already included in fontmake and then cutting a new release would be enough to cover it?

[vv-monsalve]

Pending on support for variations of gradients

• Maximizing color for FoldIt  googlefonts/nanoemoji#438 (comment)
• colr_to_svg: Support Format 5 (PaintVarLinearGradient) googlefonts/nanoemoji#426

[anthrotype]

just to clarify once again, "support for variations of gradients" does not mean that the SVG table converted from COLRv1 will contain variations (that's unsupported in the format), simply means maximum_color will henceforth ignore variation data in COLR table when generating the SVG table which will then only contain paths/gradients from the default VF instance.

[anthrotype]

@vv-monsalve @m4rc1e I'm working on it right now. Note that since we drop all variations and only leave the default instance in the SVG, the Thin weight will be displayed for those environments that only support OT-SVG and not COLRv1 (e.g. Safari/FireFox, macOS, iOS, Adobe apps etc.). E.g. this is the Finder preview on macOS:

If you wanted a more "regular" weight to be shown by default you'd have to change the default master to be the Regular (if there's one, haven't looked at your source). If you are fine with it, never mind ignore my comment.

[anthrotype]

/cc @SophiaDesign

[anthrotype]

FYI googlefonts/nanoemoji#439

[vv-monsalve]

Thanks for the expanded clarification @anthrotype.

simply means maximum_color will henceforth ignore variation data in COLR table when generating the SVG table which will then only contain paths/gradients from the default VF instance

Would it mean that the same gradients would be used for the wider-bolder instances? As Dave said in one comment of the issues:

is a new variable color font that makes extensive use of color variations (amusingly in a way to create the illusion that as the weight (and natural width) changes, the gradients look like they don't change, which requires them TO change

So, would that effect be lost in the resulting VF if the SVG table will contain only the gradients of the font origin?

Thin weight will be displayed for those environments that only support OT-SVG and not COLRv1 (e.g. Safari/FireFox, macOS, iOS, Adobe apps etc.)

I don't think this is an issue.

[anthrotype]

Would it mean that the same gradients would be used for the wider-bolder instances?

yes - not just the gradient geometries, the shapes themselves will not vary, SVG simply can't encode OT variations. The rest of the font may be variable, and that's actually a problem because if you select anything other than the Thin instance it will look wrong (outlines of the thin, too wide metrics for the selected non-Thin instance). see googlefonts/nanoemoji#439 (comment)

[SophiaDesign]

If you wanted a more "regular" weight to be shown by default you'd have to change the default master to be the Regular (if there's one, haven't looked at your source). If you are fine with it, never mind ignore my comment.

There is no Regular master in the source file. It was removed to minimise the file size. Can be added easily if preferred?

[vv-monsalve]

There is no Regular master in the source file. It was removed to minimise the file size. Can be added easily if preferred?

I think this isn't needed because of the reasons provided on the related issues and Marc's comment in the above issue.

To my understanding, when he says that is better to leave the font as is this implies:

• Not to run the maximum_color (so we wouldn't have the hybrid COLRv1+SVG when the COLR table contains variations since a B/N VF is preferable rather than having only the SVG of the font origin)
• We release it with a note to users in the description file
• Should we still wait for the latest version of Chrome?
• Would it be something else be necessary?

cc @m4rc1e, @chrissimpkins, @davelab6

[chrissimpkins]

This family remains blocked for technical reasons and should not be moved beyond dev until further notice. It is appropriately labeled blocked.