Lemonada v4.005 (stat fix) #3640

aaronbell · 2021-08-03T20:25:06Z

Font repro updated to the UFR format (https://github.com/Gue3bara/Lemonada).

Font files rebuilt.

aaronbell · 2021-08-03T20:28:45Z

Fontbakery report

Fontbakery version: 0.8.0

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

com.google.fonts/check/ftxvalidator_is_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/main/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

⚠ WARN Could not find ftxvalidator. [code: ftxvalidator-available]

[4] Lemonada[wght].ttf

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

com.google.fonts/check/metadata/designer_profiles
🔥 FAIL Designer Mohamed Gaber listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]
🔥 FAIL Designer Eduardo Tunni listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]
🔥 FAIL Designer Eduardo Tunni still does not have an avatar image. Please provide one. [code: missing-avatar]

⚠ WARN: Check copyright namerecords match license file.

com.google.fonts/check/name/license

--- Rationale ---
A known licensing description must be provided in the NameID 14 (LICENSE
DESCRIPTION) entries of the name table.
The source of truth for this check (to determine which license is in use) is a
file placed side-by-side to your font project including the licensing terms.
Depending on the chosen license, one of the following string snippets is
expected to be found on the NameID 13 (LICENSE DESCRIPTION) entries of the name
table:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.

⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN For now we're still accepting http URLs, but you should consider using https instead.
[code: http]

⚠ WARN: License URL matches License text on name table?

com.google.fonts/check/name/license_url

--- Rationale ---
A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry
of the name table.
The source of truth for this check is the licensing text found on the NameID 13
entry (LICENSE DESCRIPTION).
The string snippets used for detecting licensing terms are:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.

⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
⚠ WARN For now we're still accepting http URLs, but you should consider using https instead.
[code: http]

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.

com.google.fonts/check/meta/script_lang_tags

--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.

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

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	4	49	9	150	0
0%	0%	2%	23%	4%	70%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

gf-bot · 2021-08-05T10:11:22Z

Fontbakery report

Fontbakery version: 0.8.0

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

com.google.fonts/check/ftxvalidator_is_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/main/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

⚠ WARN Could not find ftxvalidator. [code: ftxvalidator-available]

[5] Lemonada[wght].ttf

💔 ERROR: Familyname must be unique according to namecheck.fontdata.com

com.google.fonts/check/fontdata_namecheck

--- Rationale ---
We need to check names are not already used, and today the best place to check
that is http://namecheck.fontdata.com

💔 ERROR Failed to access: http://namecheck.fontdata.com.
This check relies on the external service http://namecheck.fontdata.com via the internet. While the service cannot be reached or does not respond this check is broken.

  You can exclude this check with the command line option:
  -x com.google.fonts/check/fontdata_namecheck

  Or you can wait until the service is available again.
  If the problem persists please report this issue at: https://github.com/googlefonts/fontbakery/issues

  Original error message:
  <class 'requests.exceptions.ReadTimeout'> [code: namecheck-service]

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

com.google.fonts/check/metadata/designer_profiles
🔥 FAIL Designer Mohamed Gaber listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]
🔥 FAIL Designer Eduardo Tunni listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]
🔥 FAIL Designer Eduardo Tunni still does not have an avatar image. Please provide one. [code: missing-avatar]

⚠ WARN: Check copyright namerecords match license file.

com.google.fonts/check/name/license

--- Rationale ---
A known licensing description must be provided in the NameID 14 (LICENSE
DESCRIPTION) entries of the name table.
The source of truth for this check (to determine which license is in use) is a
file placed side-by-side to your font project including the licensing terms.
Depending on the chosen license, one of the following string snippets is
expected to be found on the NameID 13 (LICENSE DESCRIPTION) entries of the name
table:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.

⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN For now we're still accepting http URLs, but you should consider using https instead.
[code: http]

⚠ WARN: License URL matches License text on name table?

com.google.fonts/check/name/license_url

--- Rationale ---
A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry
of the name table.
The source of truth for this check is the licensing text found on the NameID 13
entry (LICENSE DESCRIPTION).
The string snippets used for detecting licensing terms are:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.

⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
⚠ WARN For now we're still accepting http URLs, but you should consider using https instead.
[code: http]

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.

com.google.fonts/check/meta/script_lang_tags

--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.

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

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
1	1	4	49	9	149	0
0%	0%	2%	23%	4%	70%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

m4rc1e · 2021-08-05T10:16:56Z

Fractions are worse

Gdef could also be improved (see report.html in the gh artifact)

RosaWagner · 2021-08-05T10:30:57Z

and fl and fi are missing

thlinard · 2021-08-05T10:31:17Z

Ł is wrong.

aaronbell · 2021-08-11T23:19:01Z

I've made a number of improvements to the font sources:

modified fraction / percents. Apparently these were set to be automatic alignment and at some point things got changed, but I couldn't find the last time they looked the way they were in the GF version. Turned off automatic alignment and re-aligned.
both fl and fi had been set to 'non-exporting' for some reason. Re-enabled them.
Fixed lslash and Lslash design.

@m4rc1e I wasn't sure what to do about your suggestion regarding the GDEF. The glyphs that have changed are all in the Arabic Presentation Form set. I suspect there has been a change to how fontmake categorizes those glyphs since this font was last exported. Do you know if that's true?

Otherwise, I think that the font is looking alright.
qa.zip

gf-bot · 2021-08-11T23:29:38Z

Fontbakery report

Fontbakery version: 0.8.0

[1] Family checks

⚠ WARN: Is the command `ftxvalidator` (Apple Font Tool Suite) available?

com.google.fonts/check/ftxvalidator_is_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/main/prebuilt/workarounds
/ftxvalidator/ssh-implementation/ftxvalidator

⚠ WARN Could not find ftxvalidator. [code: ftxvalidator-available]

[4] Lemonada[wght].ttf

🔥 FAIL: METADATA.pb: Designer is listed with the correct name on the Google Fonts catalog of designers?

com.google.fonts/check/metadata/designer_profiles
🔥 FAIL Designer Mohamed Gaber listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]
🔥 FAIL Designer Eduardo Tunni listed a Google Plus link on the catalog, but that service is not available anymore. Please update the webpage link. [code: google-plus]
🔥 FAIL Designer Eduardo Tunni still does not have an avatar image. Please provide one. [code: missing-avatar]

⚠ WARN: Check copyright namerecords match license file.

com.google.fonts/check/name/license

--- Rationale ---
A known licensing description must be provided in the NameID 14 (LICENSE
DESCRIPTION) entries of the name table.
The source of truth for this check (to determine which license is in use) is a
file placed side-by-side to your font project including the licensing terms.
Depending on the chosen license, one of the following string snippets is
expected to be found on the NameID 13 (LICENSE DESCRIPTION) entries of the name
table:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.

⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN For now we're still accepting http URLs, but you should consider using https instead.
[code: http]

⚠ WARN: License URL matches License text on name table?

com.google.fonts/check/name/license_url

--- Rationale ---
A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry
of the name table.
The source of truth for this check is the licensing text found on the NameID 13
entry (LICENSE DESCRIPTION).
The string snippets used for detecting licensing terms are:
- "This Font Software is licensed under the SIL Open Font License, Version 1.1.
This license is available with a FAQ at: https://scripts.sil.org/OFL"
- "Licensed under the Apache License, Version 2.0"
- "Licensed under the Ubuntu Font Licence 1.0."
Currently accepted licenses are Apache or Open Font License.
For a small set of legacy families the Ubuntu Font License may be acceptable as
well.
When in doubt, please choose OFL for new font projects.

⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
⚠ WARN Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=14] [code: http-in-license-info]
⚠ WARN For now we're still accepting http URLs, but you should consider using https instead.
[code: http]

⚠ WARN: Ensure fonts have ScriptLangTags declared on the 'meta' table.

com.google.fonts/check/meta/script_lang_tags

--- Rationale ---
The OpenType 'meta' table originated at Apple. Microsoft added it to OT with
just two DataMap records:
- dlng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font is designed for
- slng: comma-separated ScriptLangTags that indicate which scripts, or languages
and scripts, with possible variants, the font supports
The slng structure is intended to describe which languages and scripts the font
overall supports. For example, a Traditional Chinese font that also contains
Latin characters, can indicate Hant,Latn, showing that it supports Hant, the
Traditional Chinese variant of the Hani script, and it also supports the Latn
script
The dlng structure is far more interesting. A font may contain various glyphs,
but only a particular subset of the glyphs may be truly "leading" in the design,
while other glyphs may have been included for technical reasons. Such a
Traditional Chinese font could only list Hant there, showing that it’s designed
for Traditional Chinese, but the font would omit Latn, because the developers
don’t think the font is really recommended for purely Latin-script use.
The tags used in the structures can comprise just script, or also language and
script. For example, if a font has Bulgarian Cyrillic alternates in the locl
feature for the cyrl BGR OT languagesystem, it could also indicate in dlng
explicitly that it supports bul-Cyrl. (Note that the scripts and languages in
meta use the ISO language and script codes, not the OpenType ones).
This check ensures that the font has the meta table containing the slng and dlng
structures.
All families in the Google Fonts collection should contain the 'meta' table.
Windows 10 already uses it when deciding on which fonts to fall back to. The
Google Fonts API and also other environments could use the data for smarter
filtering. Most importantly, those entries should be added to the Noto fonts.
In the font making process, some environments store this data in external files
already. But the meta table provides a convenient way to store this inside the
font file, so some tools may add the data, and unrelated tools may read this
data. This makes the solution much more portable and universal.

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

Summary

💔 ERROR	🔥 FAIL	⚠ WARN	💤 SKIP	ℹ INFO	🍞 PASS	🔎 DEBUG
0	1	4	49	9	150	0
0%	0%	2%	23%	4%	70%	0%

Note: The following loglevels were omitted in this report:

SKIP
INFO
PASS
DEBUG

RosaWagner · 2021-08-13T10:37:06Z

LGTM thanks Aaron
Unblock #1952

Updating to UFR, fonts rebuilt.

1eacc75

aaronbell added I VF I Font Upgrade labels Aug 3, 2021

Bump version string

cefe77d

This was referenced Aug 4, 2021

MS Office for Mac as a STAT-related bug catcher #3267

Closed

STAT table errors in variable fonts #2391

Open

Weight Axis for VF: please add one intermediate named instance every 100 units systematically #3411

Open

RosaWagner self-assigned this Aug 5, 2021

RosaWagner added -- Needs Upstream Resolution Upstream fix required before moving forward and removed - Ready for Review labels Aug 5, 2021

RosaWagner mentioned this pull request Aug 5, 2021

Fix remaining Multiple Designers tag #3577

Closed

11 tasks

Updating fonts per error reporting

433eb8f

aaronbell added - Ready for Review and removed -- Needs Upstream Resolution Upstream fix required before moving forward labels Aug 11, 2021

RosaWagner added --- to_sandbox and removed - Ready for Review labels Aug 13, 2021

RosaWagner merged commit 0a30591 into main Aug 13, 2021

RosaWagner deleted the lemonada_stat branch August 13, 2021 10:37

RosaWagner added --- to_production and removed --- to_sandbox labels Aug 26, 2021

RosaWagner removed the --- to_production label Sep 22, 2021

RosaWagner added the --- Live Font is visible on API label Sep 22, 2021

RosaWagner added I Small Fix bugs fixed but nothing added and removed I Font Upgrade labels Dec 9, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Lemonada v4.005 (stat fix) #3640

Lemonada v4.005 (stat fix) #3640

aaronbell commented Aug 3, 2021

aaronbell commented Aug 3, 2021

gf-bot commented Aug 5, 2021

m4rc1e commented Aug 5, 2021 •

edited

Loading

RosaWagner commented Aug 5, 2021

thlinard commented Aug 5, 2021

aaronbell commented Aug 11, 2021

gf-bot commented Aug 11, 2021

RosaWagner commented Aug 13, 2021 •

edited

Loading

Lemonada v4.005 (stat fix) #3640

Lemonada v4.005 (stat fix) #3640

Conversation

aaronbell commented Aug 3, 2021

aaronbell commented Aug 3, 2021

Fontbakery report

Summary

gf-bot commented Aug 5, 2021

Fontbakery report

Summary

m4rc1e commented Aug 5, 2021 • edited Loading

RosaWagner commented Aug 5, 2021

thlinard commented Aug 5, 2021

aaronbell commented Aug 11, 2021

gf-bot commented Aug 11, 2021

Fontbakery report

Summary

RosaWagner commented Aug 13, 2021 • edited Loading

m4rc1e commented Aug 5, 2021 •

edited

Loading

RosaWagner commented Aug 13, 2021 •

edited

Loading