Closed eliheuer closed 7 months ago
Google Fonts onboarding uses FontBakery for QA. All FAIL level checks from the universal, opentype and googlefonts profiles must be passing in order to onboard fonts to Google Fonts. Exceptions can be made if necessary.
FAIL
universal
opentype
googlefonts
See the Quality Assurance section of the Google Fonts Guide for more information: https://googlefonts.github.io/gf-guide/qa.html
🔥 FAIL: Checking OS/2 fsType does not impose restrictions. (com.google.fonts/check/fstype)
🔥 FAIL In this font fsType is set to 8 meaning that: The font may be embedded but must only be installed temporarily on other systems.
No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
See the Google Fonts Guide for more information: https://googlefonts.github.io/gf-guide
This should be fixed in the latest version (v1.012) of the fonts.
Google Fonts onboarding uses FontBakery for QA. All
FAIL
level checks from theuniversal
,opentype
andgooglefonts
profiles must be passing in order to onboard fonts to Google Fonts. Exceptions can be made if necessary.See the Quality Assurance section of the Google Fonts Guide for more information: https://googlefonts.github.io/gf-guide/qa.html
🔥 FAIL: Checking OS/2 fsType does not impose restrictions. (com.google.fonts/check/fstype)
🔥 FAIL In this font fsType is set to 8 meaning that: The font may be embedded but must only be installed temporarily on other systems.
No such DRM restrictions can be enabled on the Google Fonts collection, so the fsType field must be set to zero (Installable Embedding) instead.
See the Google Fonts Guide for more information: https://googlefonts.github.io/gf-guide