🔥 FAILS reported on Roman VF

[vv-monsalve]

The main Fails reported on the Roman VF Fraunces[SOFT,WONK,opsz,wght].ttf are on the Typographic Subfamily Name for Windows (Name ID 17) and Instance Names. The latter must be related to what is required according to the Spec about Instances.

Note: Despite the Italic font couldn't be produced for an Error when running the build.sh, this same Fails would be expected for that font too.

🔥 FAIL: Check name table: TYPOGRAPHIC_SUBFAMILY_NAME entries.

• com.google.fonts/check/name/typographicsubfamilyname

• 🔥 FAIL TYPOGRAPHIC_SUBFAMILY_NAME for Win "144pt S100 Black" is incorrect. It must be "Black". [code: bad-typo-win]

🔥 FAIL: Check variable font instances have correct names

• com.google.fonts/check/varfont_instance_names

• 🔥 FAIL Following instances are not supported:

  • 9pt S000 Thin
  • 9pt S000 Light
  • 9pt S000 Regular
  • 9pt S000 SemiBold
  • 9pt S000 Bold
  • 9pt S000 Black
  • 9pt S050 Thin
  • 9pt S050 Light
  • 9pt S050 Regular
  • 9pt S050 SemiBold
  • 9pt S050 Bold
  • 9pt S050 Black
  • 9pt S100 Thin
  • 9pt S100 Light
  • 9pt S100 Regular
  • 9pt S100 SemiBold
  • 9pt S100 Bold
  • 9pt S100 Black
  • 72pt S000 Thin
  • 72pt S000 Light
  • 72pt S000 Regular
  • 72pt S000 SemiBold
  • 72pt S000 Bold
  • 72pt S000 Black
  • 72pt S050 Thin
  • 72pt S050 Light
  • 72pt S050 Regular
  • 72pt S050 SemiBold
  • 72pt S050 Bold
  • 72pt S050 Black
  • 72pt S100 Thin
  • 72pt S100 Light
  • 72pt S100 Regular
  • 72pt S100 SemiBold
  • 72pt S100 Bold
  • 72pt S100 Black
  • 144pt S000 Thin
  • 144pt S000 Light
  • 144pt S000 Regular
  • 144pt S000 SemiBold
  • 144pt S000 Bold
  • 144pt S000 Black
  • 144pt S050 Thin
  • 144pt S050 Light
  • 144pt S050 Regular
  • 144pt S050 SemiBold
  • 144pt S050 Bold
  • 144pt S050 Black

Further info can be found in our spec https://github.com/googlefonts/gf-docs/tree/master/Spec#fvar-instances [code: bad-instance-names]

[sponcey]

In issue #209, @davelab6 said that this first fail can be ignored.

The second fail, I'm not sure about that one. Perhaps @davelab6 can clarify: Is this spec going to be updated, since Fraunces needs to have instance names that reflect its multiple axes?

[davelab6]

@m4rc1e can better answer this.

[davelab6]

Re-reading this, the GF Spec policy at the moment is to limit the fvar instances to the "Weight Width Slope" model from Windows Vista+. The other styles should be named in the STAT table. @vv-monsalve can handle this