Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Syne: v-2.000 added #2644

Merged
merged 1 commit into from
Aug 26, 2020
Merged

Syne: v-2.000 added #2644

merged 1 commit into from
Aug 26, 2020

Conversation

RosaWagner
Copy link
Contributor

Fontbakery report — VARIABLE

Fontbakery version: 0.7.29

[1] Family checks
🔥 FAIL: Do we have the latest version of FontBakery installed?

[2] Syne[wght].ttf
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: Is there kerning info for non-ligated sequences? 
--- Rationale ---

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).

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

    • f + f
    • f + i
    • i + f

    [code: lacks-kern-info]


Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 1 2 77 7 90 0
0% 1% 1% 44% 4% 51% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS
  • DEBUG

Fontbakery report - STATIC UPRIGHTS

Fontbakery version: 0.7.29

[1] Family checks
🔥 FAIL: Do we have the latest version of FontBakery installed?

[3] Syne-Bold.ttf
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: Check if each glyph has the recommended amount of contours. 
--- Rationale ---

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.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

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.
  • ⚠ WARN 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.

The following glyphs do not have the recommended number of contours:

Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: trademark Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: arrowboth Contours detected: 2 Expected: 1
Glyph name: arrowupdn Contours detected: 2 Expected: 1
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: arrowupdn Contours detected: 2 Expected: 1
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: arrowboth Contours detected: 2 Expected: 1
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: fi Contours detected: 1 Expected: 3
Glyph name: trademark Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1 [code: contour-count]

⚠ WARN: Is there kerning info for non-ligated sequences? 
--- Rationale ---

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).

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

    • f + f
    • f + i
    • i + f

    [code: lacks-kern-info]


[3] Syne-ExtraBold.ttf
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: Check if each glyph has the recommended amount of contours. 
--- Rationale ---

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.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

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.
  • ⚠ WARN 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.

The following glyphs do not have the recommended number of contours:

Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: trademark Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: fi Contours detected: 1 Expected: 3
Glyph name: trademark Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1 [code: contour-count]

⚠ WARN: Is there kerning info for non-ligated sequences? 
--- Rationale ---

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).

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

    • f + f
    • f + i
    • i + f

    [code: lacks-kern-info]


[3] Syne-Regular.ttf
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: Check if each glyph has the recommended amount of contours. 
--- Rationale ---

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.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

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.
  • ⚠ WARN 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.

The following glyphs do not have the recommended number of contours:

Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: trademark Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: fi Contours detected: 1 Expected: 3
Glyph name: trademark Contours detected: 3 Expected: 2
Glyph name: hbar Contours detected: 2 Expected: 1 [code: contour-count]

⚠ WARN: Is there kerning info for non-ligated sequences? 
--- Rationale ---

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).

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

    • f + f
    • f + i
    • i + f

    [code: lacks-kern-info]


Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 1 9 235 18 240 0
0% 0% 2% 47% 4% 48% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS
  • DEBUG

Fontbakery report — STATIC ITALIC

Fontbakery version: 0.7.29

[1] Family checks
🔥 FAIL: Do we have the latest version of FontBakery installed?

[3] Syne-Italic.ttf
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: Check if each glyph has the recommended amount of contours. 
--- Rationale ---

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.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

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.
  • ⚠ WARN 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.

The following glyphs do not have the recommended number of contours:

Glyph name: quotesinglbase Contours detected: 2 Expected: 1
Glyph name: quotedblbase Contours detected: 4 Expected: 2
Glyph name: bullet Contours detected: 4 Expected: 1
Glyph name: dollar Contours detected: 2 Expected: 1 or 3
Glyph name: asterisk Contours detected: 2 Expected: 1 or 4
Glyph name: comma Contours detected: 2 Expected: 1
Glyph name: one Contours detected: 2 Expected: 1
Glyph name: six Contours detected: 3 Expected: 1 or 2
Glyph name: nine Contours detected: 3 Expected: 1 or 2
Glyph name: semicolon Contours detected: 3 Expected: 2
Glyph name: guilsinglright Contours detected: 2 Expected: 1
Glyph name: equal Contours detected: 3 Expected: 2
Glyph name: greater Contours detected: 2 Expected: 1
Glyph name: A Contours detected: 3 Expected: 2
Glyph name: B Contours detected: 1 Expected: 2 or 3
Glyph name: N Contours detected: 2 Expected: 1
Glyph name: Q Contours detected: 3 Expected: 2
Glyph name: Z Contours detected: 2 Expected: 1
Glyph name: bracketleft Contours detected: 2 Expected: 1
Glyph name: a Contours detected: 9 Expected: 2
Glyph name: d Contours detected: 1 Expected: 2
Glyph name: k Contours detected: 3 Expected: 1 or 2
Glyph name: l Contours detected: 2 Expected: 1
Glyph name: q Contours detected: 3 Expected: 2
Glyph name: r Contours detected: 2 Expected: 1
Glyph name: w Contours detected: 2 Expected: 1
Glyph name: z Contours detected: 3 Expected: 1
Glyph name: braceleft Contours detected: 2 Expected: 1
Glyph name: currency Contours detected: 1 Expected: 2
Glyph name: copyright Contours detected: 2 Expected: 3
Glyph name: guillemotleft Contours detected: 3 Expected: 2
Glyph name: logicalnot Contours detected: 2 Expected: 1
Glyph name: registered Contours detected: 2 Expected: 3 or 4
Glyph name: plusminus Contours detected: 3 Expected: 1 or 2
Glyph name: Agrave Contours detected: 4 Expected: 3
Glyph name: Aacute Contours detected: 4 Expected: 3
Glyph name: Acircumflex Contours detected: 5 Expected: 3
Glyph name: Atilde Contours detected: 4 Expected: 3
Glyph name: Adieresis Contours detected: 5 Expected: 4
Glyph name: Aring Contours detected: 5 Expected: 3 or 4
Glyph name: Ecircumflex Contours detected: 3 Expected: 2
Glyph name: Icircumflex Contours detected: 3 Expected: 2
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Ntilde Contours detected: 3 Expected: 2
Glyph name: Ocircumflex Contours detected: 4 Expected: 3
Glyph name: Ucircumflex Contours detected: 3 Expected: 2
Glyph name: agrave Contours detected: 10 Expected: 3
Glyph name: aacute Contours detected: 10 Expected: 3
Glyph name: acircumflex Contours detected: 10 Expected: 3
Glyph name: atilde Contours detected: 10 Expected: 3
Glyph name: adieresis Contours detected: 11 Expected: 4
Glyph name: aring Contours detected: 11 Expected: 4
Glyph name: eth Contours detected: 1 Expected: 2
Glyph name: divide Contours detected: 5 Expected: 3
Glyph name: Amacron Contours detected: 4 Expected: 3
Glyph name: amacron Contours detected: 10 Expected: 3
Glyph name: Abreve Contours detected: 4 Expected: 3
Glyph name: abreve Contours detected: 10 Expected: 3
Glyph name: Ccaron Contours detected: 3 Expected: 2
Glyph name: Dcaron Contours detected: 4 Expected: 3
Glyph name: dcaron Contours detected: 2 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: Ecaron Contours detected: 3 Expected: 2
Glyph name: uni0122 Contours detected: 3 Expected: 2
Glyph name: uni0123 Contours detected: 5 Expected: 3 or 4
Glyph name: trademark Contours detected: 1 Expected: 2
Glyph name: less Contours detected: 2 Expected: 1
Glyph name: uni0136 Contours detected: 4 Expected: 2 or 3
Glyph name: uni0137 Contours detected: 5 Expected: 2 or 3
Glyph name: lacute Contours detected: 3 Expected: 2
Glyph name: uni013B Contours detected: 3 Expected: 2
Glyph name: uni013C Contours detected: 4 Expected: 2
Glyph name: lcaron Contours detected: 3 Expected: 2
Glyph name: ldot Contours detected: 3 Expected: 2
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: lslash Contours detected: 3 Expected: 1
Glyph name: Nacute Contours detected: 3 Expected: 2
Glyph name: uni0145 Contours detected: 4 Expected: 2
Glyph name: uni0146 Contours detected: 3 Expected: 2
Glyph name: Ncaron Contours detected: 4 Expected: 2
Glyph name: Eng Contours detected: 2 Expected: 1
Glyph name: eng Contours detected: 2 Expected: 1
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: racute Contours detected: 3 Expected: 2
Glyph name: uni0156 Contours detected: 4 Expected: 3
Glyph name: uni0157 Contours detected: 4 Expected: 2
Glyph name: Rcaron Contours detected: 4 Expected: 3
Glyph name: rcaron Contours detected: 3 Expected: 2
Glyph name: Scaron Contours detected: 3 Expected: 2
Glyph name: Tcaron Contours detected: 3 Expected: 2
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: Wcircumflex Contours detected: 3 Expected: 2
Glyph name: wcircumflex Contours detected: 3 Expected: 2
Glyph name: Ycircumflex Contours detected: 3 Expected: 2
Glyph name: Zacute Contours detected: 3 Expected: 2
Glyph name: zacute Contours detected: 4 Expected: 2
Glyph name: Zdotaccent Contours detected: 3 Expected: 2
Glyph name: zdotaccent Contours detected: 4 Expected: 2
Glyph name: Zcaron Contours detected: 4 Expected: 2
Glyph name: zcaron Contours detected: 4 Expected: 2
Glyph name: arrowup Contours detected: 2 Expected: 1
Glyph name: arrowdown Contours detected: 2 Expected: 1
Glyph name: partialdiff Contours detected: 1 Expected: 2
Glyph name: emptyset Contours detected: 2 Expected: 3
Glyph name: summation Contours detected: 3 Expected: 1
Glyph name: uni0218 Contours detected: 3 Expected: 2
Glyph name: uni0219 Contours detected: 3 Expected: 2
Glyph name: uni021A Contours detected: 3 Expected: 2
Glyph name: uni021B Contours detected: 3 Expected: 2
Glyph name: infinity Contours detected: 2 Expected: 3
Glyph name: notequal Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 3 Expected: 2
Glyph name: greaterequal Contours detected: 3 Expected: 2
Glyph name: uni0312 Contours detected: 2 Expected: 1
Glyph name: uni0326 Contours detected: 2 Expected: 1
Glyph name: uni0394 Contours detected: 3 Expected: 2
Glyph name: percent Contours detected: 4 Expected: 5
Glyph name: pi Contours detected: 2 Expected: 1
Glyph name: wgrave Contours detected: 3 Expected: 2
Glyph name: wacute Contours detected: 3 Expected: 2
Glyph name: wdieresis Contours detected: 4 Expected: 3
Glyph name: oneeighth Contours detected: 4 Expected: 5
Glyph name: threeeighths Contours detected: 4 Expected: 5
Glyph name: fiveeighths Contours detected: 4 Expected: 5
Glyph name: seveneighths Contours detected: 4 Expected: 5
Glyph name: Ntilde Contours detected: 3 Expected: 2
Glyph name: Rcaron Contours detected: 4 Expected: 3
Glyph name: Tcaron Contours detected: 3 Expected: 2
Glyph name: Atilde Contours detected: 4 Expected: 3
Glyph name: Ocircumflex Contours detected: 4 Expected: 3
Glyph name: wgrave Contours detected: 3 Expected: 2
Glyph name: bracketleft Contours detected: 2 Expected: 1
Glyph name: Icircumflex Contours detected: 3 Expected: 2
Glyph name: wacute Contours detected: 3 Expected: 2
Glyph name: Lslash Contours detected: 2 Expected: 1
Glyph name: z Contours detected: 3 Expected: 1
Glyph name: Ncaron Contours detected: 4 Expected: 2
Glyph name: lcaron Contours detected: 3 Expected: 2
Glyph name: divide Contours detected: 5 Expected: 3
Glyph name: atilde Contours detected: 10 Expected: 3
Glyph name: dollar Contours detected: 2 Expected: 1 or 3
Glyph name: wdieresis Contours detected: 4 Expected: 3
Glyph name: semicolon Contours detected: 3 Expected: 2
Glyph name: arrowup Contours detected: 2 Expected: 1
Glyph name: guilsinglright Contours detected: 2 Expected: 1
Glyph name: notequal Contours detected: 2 Expected: 1
Glyph name: N Contours detected: 2 Expected: 1
Glyph name: guillemotleft Contours detected: 3 Expected: 2
Glyph name: braceleft Contours detected: 2 Expected: 1
Glyph name: dcaron Contours detected: 2 Expected: 3
Glyph name: amacron Contours detected: 10 Expected: 3
Glyph name: uni0218 Contours detected: 3 Expected: 2
Glyph name: Eng Contours detected: 2 Expected: 1
Glyph name: A Contours detected: 3 Expected: 2
Glyph name: d Contours detected: 1 Expected: 2
Glyph name: eng Contours detected: 2 Expected: 1
Glyph name: oe Contours detected: 4 Expected: 3
Glyph name: rcaron Contours detected: 3 Expected: 2
Glyph name: q Contours detected: 3 Expected: 2
Glyph name: uni0157 Contours detected: 4 Expected: 2
Glyph name: Aring Contours detected: 5 Expected: 3 or 4
Glyph name: uni0219 Contours detected: 3 Expected: 2
Glyph name: Zcaron Contours detected: 4 Expected: 2
Glyph name: Ucircumflex Contours detected: 3 Expected: 2
Glyph name: l Contours detected: 2 Expected: 1
Glyph name: zdotaccent Contours detected: 4 Expected: 2
Glyph name: Ecaron Contours detected: 3 Expected: 2
Glyph name: agrave Contours detected: 10 Expected: 3
Glyph name: fi Contours detected: 2 Expected: 3
Glyph name: fl Contours detected: 1 Expected: 2
Glyph name: eth Contours detected: 1 Expected: 2
Glyph name: uni0123 Contours detected: 5 Expected: 3 or 4
Glyph name: comma Contours detected: 2 Expected: 1
Glyph name: lessequal Contours detected: 3 Expected: 2
Glyph name: asterisk Contours detected: 2 Expected: 1 or 4
Glyph name: Aacute Contours detected: 4 Expected: 3
Glyph name: Ycircumflex Contours detected: 3 Expected: 2
Glyph name: quotesinglbase Contours detected: 2 Expected: 1
Glyph name: Nacute Contours detected: 3 Expected: 2
Glyph name: six Contours detected: 3 Expected: 1 or 2
Glyph name: zcaron Contours detected: 4 Expected: 2
Glyph name: less Contours detected: 2 Expected: 1
Glyph name: Agrave Contours detected: 4 Expected: 3
Glyph name: greaterequal Contours detected: 3 Expected: 2
Glyph name: abreve Contours detected: 10 Expected: 3
Glyph name: k Contours detected: 3 Expected: 1 or 2
Glyph name: Abreve Contours detected: 4 Expected: 3
Glyph name: Zacute Contours detected: 3 Expected: 2
Glyph name: uni0145 Contours detected: 4 Expected: 2
Glyph name: uni0326 Contours detected: 2 Expected: 1
Glyph name: lacute Contours detected: 3 Expected: 2
Glyph name: trademark Contours detected: 1 Expected: 2
Glyph name: r Contours detected: 2 Expected: 1
Glyph name: a Contours detected: 9 Expected: 2
Glyph name: copyright Contours detected: 2 Expected: 3
Glyph name: uni0122 Contours detected: 3 Expected: 2
Glyph name: summation Contours detected: 3 Expected: 1
Glyph name: threeeighths Contours detected: 4 Expected: 5
Glyph name: zacute Contours detected: 4 Expected: 2
Glyph name: plusminus Contours detected: 3 Expected: 1 or 2
Glyph name: ldot Contours detected: 3 Expected: 2
Glyph name: uni021A Contours detected: 3 Expected: 2
Glyph name: lslash Contours detected: 3 Expected: 1
Glyph name: logicalnot Contours detected: 2 Expected: 1
Glyph name: Dcaron Contours detected: 4 Expected: 3
Glyph name: wcircumflex Contours detected: 3 Expected: 2
Glyph name: partialdiff Contours detected: 1 Expected: 2
Glyph name: aring Contours detected: 11 Expected: 4
Glyph name: currency Contours detected: 1 Expected: 2
Glyph name: Amacron Contours detected: 4 Expected: 3
Glyph name: one Contours detected: 2 Expected: 1
Glyph name: seveneighths Contours detected: 4 Expected: 5
Glyph name: bullet Contours detected: 4 Expected: 1
Glyph name: Tbar Contours detected: 2 Expected: 1
Glyph name: uni021B Contours detected: 3 Expected: 2
Glyph name: uni0146 Contours detected: 3 Expected: 2
Glyph name: uni0137 Contours detected: 5 Expected: 2 or 3
Glyph name: emptyset Contours detected: 2 Expected: 3
Glyph name: Acircumflex Contours detected: 5 Expected: 3
Glyph name: Z Contours detected: 2 Expected: 1
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Scaron Contours detected: 3 Expected: 2
Glyph name: uni0156 Contours detected: 4 Expected: 3
Glyph name: uni013B Contours detected: 3 Expected: 2
Glyph name: registered Contours detected: 2 Expected: 3 or 4
Glyph name: Ccaron Contours detected: 3 Expected: 2
Glyph name: acircumflex Contours detected: 10 Expected: 3
Glyph name: nine Contours detected: 3 Expected: 1 or 2
Glyph name: arrowdown Contours detected: 2 Expected: 1
Glyph name: Ecircumflex Contours detected: 3 Expected: 2
Glyph name: oneeighth Contours detected: 4 Expected: 5
Glyph name: w Contours detected: 2 Expected: 1
Glyph name: greater Contours detected: 2 Expected: 1
Glyph name: fiveeighths Contours detected: 4 Expected: 5
Glyph name: quotedblbase Contours detected: 4 Expected: 2
Glyph name: equal Contours detected: 3 Expected: 2
Glyph name: uni0312 Contours detected: 2 Expected: 1
Glyph name: adieresis Contours detected: 11 Expected: 4
Glyph name: aacute Contours detected: 10 Expected: 3
Glyph name: B Contours detected: 1 Expected: 2 or 3
Glyph name: Wcircumflex Contours detected: 3 Expected: 2
Glyph name: uni0136 Contours detected: 4 Expected: 2 or 3
Glyph name: Q Contours detected: 3 Expected: 2
Glyph name: infinity Contours detected: 2 Expected: 3
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: uni013C Contours detected: 4 Expected: 2
Glyph name: uni0394 Contours detected: 3 Expected: 2
Glyph name: pi Contours detected: 2 Expected: 1
Glyph name: Adieresis Contours detected: 5 Expected: 4
Glyph name: Zdotaccent Contours detected: 3 Expected: 2
Glyph name: percent Contours detected: 4 Expected: 5
Glyph name: racute Contours detected: 3 Expected: 2 [code: contour-count]

⚠ WARN: Is there kerning info for non-ligated sequences? 
--- Rationale ---

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).

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

    • c + t
    • f + f
    • f + i
    • i + f
    • i + m
    • m + n
    • n + o
    • o + r
    • r + u
    • u + y
    • s + h
    • h + t
    • z + y

    [code: lacks-kern-info]


Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 1 3 79 6 88 0
0% 1% 2% 45% 3% 50% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS
  • DEBUG

Fontbakery report — STATIC MONO

Fontbakery version: 0.7.29

[1] Family checks
🔥 FAIL: Do we have the latest version of FontBakery installed?

[3] SyneMono-Regular.ttf
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: Check if each glyph has the recommended amount of contours. 
--- Rationale ---

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.

However, a quotedbl should have 2 contours, unless the font belongs to a
display family.

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.
  • ⚠ WARN 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.

The following glyphs do not have the recommended number of contours:

Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: arrowleft Contours detected: 2 Expected: 1
Glyph name: arrowup Contours detected: 2 Expected: 1
Glyph name: arrowright Contours detected: 2 Expected: 1
Glyph name: arrowdown Contours detected: 2 Expected: 1
Glyph name: arrowboth Contours detected: 3 Expected: 1
Glyph name: uni2196 Contours detected: 2 Expected: 1
Glyph name: uni2197 Contours detected: 2 Expected: 1
Glyph name: uni2198 Contours detected: 2 Expected: 1
Glyph name: uni2199 Contours detected: 2 Expected: 1
Glyph name: arrowupdn Contours detected: 3 Expected: 1
Glyph name: uni2199 Contours detected: 2 Expected: 1
Glyph name: Dcroat Contours detected: 3 Expected: 2
Glyph name: arrowboth Contours detected: 3 Expected: 1
Glyph name: arrowdown Contours detected: 2 Expected: 1
Glyph name: uni2198 Contours detected: 2 Expected: 1
Glyph name: dcroat Contours detected: 3 Expected: 2
Glyph name: Eth Contours detected: 3 Expected: 2
Glyph name: arrowupdn Contours detected: 3 Expected: 1
Glyph name: uni2196 Contours detected: 2 Expected: 1
Glyph name: arrowup Contours detected: 2 Expected: 1
Glyph name: uni2197 Contours detected: 2 Expected: 1 [code: contour-count]

⚠ WARN: Checking correctness of monospaced metadata. 
--- Rationale ---

There are various metadata in the OpenType spec to specify if a font is
monospaced or not. If the font is not truly monospaced, then no monospaced
metadata should be set (as sometimes they mistakenly are...)

Requirements for monospace fonts:

* post.isFixedPitch - "Set to 0 if the font is proportionally spaced, non-zero
if the font is not proportionally spaced (monospaced)"
  www.microsoft.com/typography/otspec/post.htm

* hhea.advanceWidthMax must be correct, meaning no glyph's width value is
greater.
  www.microsoft.com/typography/otspec/hhea.htm

* OS/2.panose.bProportion must be set to 9 (monospace). Spec says: "The PANOSE
definition contains ten digits each of which currently describes up to sixteen
variations. Windows uses bFamilyType, bSerifStyle and bProportion in the font
mapper to determine family type. It also uses bProportion to determine if the
font is monospaced."
  www.microsoft.com/typography/otspec/os2.htm#pan
  monotypecom-test.monotype.de/services/pan2

* OS/2.xAvgCharWidth must be set accurately.
  "OS/2.xAvgCharWidth is used when rendering monospaced fonts, at least by
Windows GDI"
  http://typedrawers.com/discussion/comment/15397/#Comment_15397

Also we should report an error for glyphs not of average width.

Please also note:
Thomas Phinney told us that a few years ago (as of December 2019), if you gave
a font a monospace flag in Panose, Microsoft Word would ignore the actual
advance widths and treat it as monospaced. Source:
https://typedrawers.com/discussion/comment/45140/#Comment_45140
  • ⚠ WARN Font is monospaced but 39 glyphs (6.4144736842105265%) have a different width. You should check the widths of: ['fraction', 'onehalf', 'onequarter', 'threequarters', 'CR', 'uni0308', 'uni0307', 'gravecomb', 'acutecomb', 'uni030B', 'uni030C.alt', 'uni0302', 'uni030C', 'uni0306', 'uni030A', 'tildecomb', 'uni0304', 'uni0312', 'uni0326', 'uni0327', 'uni0328', 'gravecomb.ss03', 'acutecomb.ss03', 'uni030B.ss03', 'uni030C.alt.ss03', 'uni0302.ss03', 'uni030C.ss03', 'uni0306.ss03', 'uni030A.ss03', 'tildecomb.ss03', 'uni0304.ss03', 'uni0312.ss03', 'uni0326.ss03', 'uni0327.ss03', 'uni0328.ss03', 'uni0335.ss03', 'uni0336.ss03', 'uni0337.ss03', 'uni0338.ss03'] [code: mono-outliers]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 1 3 81 6 86 0
0% 1% 2% 46% 3% 49% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS
  • DEBUG

@gf-bot
Copy link

gf-bot commented Aug 25, 2020

Fontbakery report

Fontbakery version: 0.7.29

[1] Family checks
⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available? 
--- Rationale ---

There's no reasonable (and legal) way to run the command `ftxvalidator` of the
Apple Font Tool Suite on a non-macOS machine. I.e. on GNU+Linux or Windows etc.

If Font Bakery is not running on an OSX machine, the machine running Font
Bakery could access `ftxvalidator` on OSX, e.g. via ssh or a remote procedure
call (rpc).

There's an ssh example implementation at:
https://github.com/googlefonts/fontbakery/blob/master/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator
  • ⚠ WARN Could not find ftxvalidator.

[4] Syne[wght].ttf
🔥 FAIL: DESCRIPTION.en_us.html must have less than 1000 bytes.
⚠ WARN: Checking OS/2 achVendID. 
--- Rationale ---

Microsoft keeps a list of font vendors and their respective contact info. This
list is updated regularly and is indexed by a 4-char "Vendor ID" which is
stored in the achVendID field of the OS/2 table.

Registering your ID is not mandatory, but it is a good practice since some
applications may display the type designer / type foundry contact info on some
dialog and also because that info will be visible on Microsoft's website:

https://docs.microsoft.com/en-us/typography/vendors/

This check verifies whether or not a given font's vendor ID is registered in
that list or if it has some of the default values used by the most common font
editors.

Each new FontBakery release includes a cached copy of that list of vendor IDs.
If you registered recently, you're safe to ignore warnings emitted by this
check, since your ID will soon be included in one of our upcoming releases.
  • ⚠ WARN OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
    [code: unknown]
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API?
⚠ WARN: Is there kerning info for non-ligated sequences? 
--- Rationale ---

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).

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

    • f + f
    • f + i
    • i + f

    [code: lacks-kern-info]


Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 1 4 36 9 127 0
0% 1% 2% 20% 5% 72% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • INFO
  • PASS
  • DEBUG

Diff images: qa.zip

@RosaWagner RosaWagner mentioned this pull request Aug 25, 2020
Closed
@RosaWagner RosaWagner linked an issue Aug 25, 2020 that may be closed by this pull request
Add Syne #2075
Closed
@m4rc1e m4rc1e merged commit a3aa3c2 into master Aug 26, 2020
@m4rc1e m4rc1e deleted the syne branch August 26, 2020 10:22
@m4rc1e
Copy link
Collaborator

m4rc1e commented Aug 26, 2020

Thanks @RosaWagner!

@davelab6
Copy link
Member

davelab6 commented Sep 9, 2020

@RosaWagner

Note: The mono and the italic are separated designs from the uprights, but they are all part of the same family.

Sadly, this doesn't fit the way Google Fonts API works.

SyneMono-Regular.ttf needs to be added as a separate sibling family, and Syne-Italic.ttf needs to be removed until it has the same range of Weight axis as the roman.

Since those 2 files are currently in the static folder of this repo, I will just remove them now; the static subdirectory is only used for families which previously had some form of hinting that we want to serve to non-VF capable web browsers.

@davelab6
Copy link
Member

davelab6 commented Sep 9, 2020

Also since there are only 3 static fonts in /ofl/syne/static then I've removed them all in my pr #2674, the API would require a "full house" of all "x 100" OS/2 value Weight axis instance locations between 100 and 900m, but this had 400, 700, 800 - so missing the 500 and 600.

@davelab6 davelab6 mentioned this pull request Sep 9, 2020
Open
davelab6 added a commit that referenced this pull request Sep 9, 2020
@davelab6
Update to_sandbox.txt
3b371af 
Jost #2627, Rubik #2664, Sansita Swashed #2658, Piazzolla #2653, Baskervville Epilogue Grandstander #2648, Merriweather #2632, Syne #2644
@RosaWagner RosaWagner added the --- Live Font is visible on API label Sep 9, 2020
davelab6 pushed a commit that referenced this pull request Dec 10, 2020
@RosaWagner @davelab6
Syne: v-2.000 added (#2644)
bf1b11f
davelab6 added a commit that referenced this pull request Dec 10, 2020
@davelab6
Update to_sandbox.txt
e3b33c2 
Jost #2627, Rubik #2664, Sansita Swashed #2658, Piazzolla #2653, Baskervville Epilogue Grandstander #2648, Merriweather #2632, Syne #2644
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
--- Live Font is visible on API
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Add Syne
4 participants
@RosaWagner @gf-bot @m4rc1e @davelab6