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.

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

Mooli: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added #6585

Merged
merged 3 commits into from
Aug 30, 2023

Conversation

emmamarichal
Copy link
Collaborator

819b113: [gftools-packager] Mooli: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added

dd520c8: Description added

@emmamarichal emmamarichal linked an issue Aug 2, 2023 that may be closed by this pull request
9 tasks
@github-actions
Copy link

github-actions bot commented Aug 2, 2023

Fontbakery report

Fontbakery version: 0.8.13

[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, 1 of them (100.00%) lack a STAT table.

    And these are the most common STAT axis orderings:
    [code: summary]


[18] Mooli-Regular.ttf
💔 ERROR: Familyname must be unique according to namecheck.fontdata.com (com.google.fonts/check/fontdata_namecheck)
  • 💔 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.ConnectionError'> [code: namecheck-service]
    
WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)
  • WARN OS/2 VendorID value 'NeWT' 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 for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)
  • WARN The following codepoints supported by the font are not covered by
    any subsets defined in the font's metadata file, and will never
    be served. You can solve this by either manually adding additional
    subset declarations to METADATA.pb, or by editing the glyphset
    definitions.

  • U+02C7 CARON: try adding one of: tifinagh, yi, canadian-aboriginal

  • U+02D8 BREVE: try adding one of: yi, canadian-aboriginal

  • U+02D9 DOT ABOVE: try adding one of: yi, canadian-aboriginal

  • U+02DB OGONEK: try adding one of: yi, canadian-aboriginal

  • U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: coptic, tifinagh, cherokee, math

  • U+0306 COMBINING BREVE: try adding one of: tifinagh, old-permic

  • U+0307 COMBINING DOT ABOVE: try adding one of: malayalam, tai-le, canadian-aboriginal, syriac, tifinagh, coptic, math, old-permic

  • U+030A COMBINING RING ABOVE: try adding syriac

  • U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee

  • U+030C COMBINING CARON: try adding one of: tai-le, cherokee
    18 more.

Use -F or --full-lists to disable shortening of long lists.

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu [code: unreachable-subsetting]

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 + i

    • 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: 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 if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)
  • 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: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: Racute	Contours detected: 3	Expected: 2

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: uni1E9E	Contours detected: 2	Expected: 1

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: fi	Contours detected: 2	Expected: 3

- Glyph name: uni1E9E	Contours detected: 2	Expected: 1 

- Glyph name: uogonek	Contours detected: 2	Expected: 1

[code: contour-count]

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]
WARN: Are there any misaligned on-curve points? (com.google.fonts/check/outline_alignment_miss)
  • WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:

    • S (U+0053): X=854.0,Y=1457.5 (should be at cap-height 1456?)

    • V (U+0056): X=581.0,Y=1.0 (should be at baseline 0?)

    • V (U+0056): X=767.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=654.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=441.0,Y=1.0 (should be at baseline 0?)

    • a (U+0061): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • b (U+0062): X=387.5,Y=0.5 (should be at baseline 0?)

    • g (U+0067): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • k (U+006B): X=177.0,Y=-1.5 (should be at baseline 0?)

    • r (U+0072): X=778.0,Y=1028.0 (should be at x-height 1026?)

    • 20 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments]

WARN: Are any segments inordinately short? (com.google.fonts/check/outline_short_segments)
  • WARN The following glyphs have segments which seem very short:

    • at (U+0040) contains a short segment B<<1226.0,436.0>-<1226.0,394.0>-<1245.0,372.0>>

    • at (U+0040) contains a short segment B<<1245.0,372.0>-<1264.0,350.0>-<1309.0,350.0>>

    • w (U+0077) contains a short segment B<<480.0,186.0>-<488.0,207.0>-<495.0,231.5>>

    • w (U+0077) contains a short segment B<<495.0,231.5>-<502.0,256.0>-<511.0,276.0>>

    • w (U+0077) contains a short segment B<<1190.0,286.0>-<1198.0,265.0>-<1205.0,238.5>>

    • y (U+0079) contains a short segment B<<269.0,1026.0>-<271.0,1021.0>-<287.5,986.0>>

    • braceleft (U+007B) contains a short segment L<<86.0,676.0>--<88.0,675.0>>

    • braceright (U+007D) contains a short segment L<<566.0,553.0>--<564.0,554.0>>

    • sterling (U+00A3) contains a short segment B<<296.0,832.0>-<295.0,840.0>-<294.5,847.0>>

    • sterling (U+00A3) contains a short segment B<<294.5,847.0>-<294.0,854.0>-<294.0,861.0>>

    • 36 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)
  • WARN The following glyphs have colinear vectors:

    • Eng (U+014A): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Eng (U+014A): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • M (U+004D): L<<1602.0,1251.0>--<1534.0,1096.0>> -> L<<1534.0,1096.0>--<1034.0,110.0>>

    • M (U+004D): L<<412.0,1456.0>--<887.0,526.0>> -> L<<887.0,526.0>--<973.0,322.0>>

    • M (U+004D): L<<973.0,322.0>--<1058.0,529.0>> -> L<<1058.0,529.0>--<1536.0,1456.0>>

    • N (U+004E): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • N (U+004E): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Nacute (U+0143): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Nacute (U+0143): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Ncaron (U+0147): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • 32 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-colinear-vectors]

INFO: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)
INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
  • INFO Hinting filesize impact:
ofl/mooli/Mooli-Regular.ttf
Dehinted Size 43.1kb
Hinted Size 60.8kb
Increase 17.8kb
Change 41.3 %
[code: size-impact]
INFO: EPAR table present in font? (com.google.fonts/check/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.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33]"
    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: Font contains all required tables? (com.google.fonts/check/required_tables)
  • INFO This font contains the following optional tables:

    • cvt

    • fpgm

    • loca

    • prep

    • GPOS

    • GSUB

    • gasp [code: optional-tables]

INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • INFO ofl/mooli [code: family-path]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
1 0 10 63 8 164 0
0% 0% 4% 26% 3% 67% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • PASS
  • DEBUG

@RosaWagner RosaWagner self-requested a review August 29, 2023 10:00
@RosaWagner
Copy link
Contributor

RosaWagner commented Aug 29, 2023

Noticed Germandbls is a not glyphs instead of the actual glyphs. Since Mulish has the glyphs, could be easy to copy-paste and adjust.

ofl/mooli/METADATA.pb Outdated Show resolved Hide resolved
ofl/mooli/DESCRIPTION.en_us.html Outdated Show resolved Hide resolved
@RosaWagner RosaWagner added the -- Needs Upstream Resolution Upstream fix required before moving forward label Aug 29, 2023
@github-actions
Copy link

FontBakery report

fontbakery version: 0.9.0a2

[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, 1 of them (100.00%) lack a STAT table.

    And these are the most common STAT axis orderings:
    [code: summary]


[17] Mooli-Regular.ttf
WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)
  • WARN OS/2 VendorID value 'NeWT' 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 for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)
  • WARN The following codepoints supported by the font are not covered by
    any subsets defined in the font's metadata file, and will never
    be served. You can solve this by either manually adding additional
    subset declarations to METADATA.pb, or by editing the glyphset
    definitions.

  • U+02C7 CARON: try adding one of: canadian-aboriginal, yi, tifinagh

  • U+02D8 BREVE: try adding one of: canadian-aboriginal, yi

  • U+02D9 DOT ABOVE: try adding one of: canadian-aboriginal, yi

  • U+02DB OGONEK: try adding one of: canadian-aboriginal, yi

  • U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: math, cherokee, coptic, tifinagh

  • U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh

  • U+0307 COMBINING DOT ABOVE: try adding one of: old-permic, canadian-aboriginal, tai-le, syriac, tifinagh, math, malayalam, coptic

  • U+030A COMBINING RING ABOVE: try adding syriac

  • U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: cherokee, osage

  • U+030C COMBINING CARON: try adding one of: tai-le, cherokee
    18 more.

Use -F or --full-lists to disable shortening of long lists.

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu [code: unreachable-subsetting]

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 + i

    • 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: 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 if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)
  • 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: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: Racute	Contours detected: 3	Expected: 2

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: uni1E9E	Contours detected: 2	Expected: 1

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: fi	Contours detected: 2	Expected: 3

- Glyph name: uni1E9E	Contours detected: 2	Expected: 1

- Glyph name: uogonek	Contours detected: 2	Expected: 1

[code: contour-count]

WARN: Are there any misaligned on-curve points? (com.google.fonts/check/outline_alignment_miss)
  • WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:

    • S (U+0053): X=854.0,Y=1457.5 (should be at cap-height 1456?)

    • V (U+0056): X=581.0,Y=1.0 (should be at baseline 0?)

    • V (U+0056): X=767.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=654.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=441.0,Y=1.0 (should be at baseline 0?)

    • a (U+0061): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • b (U+0062): X=387.5,Y=0.5 (should be at baseline 0?)

    • g (U+0067): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • k (U+006B): X=177.0,Y=-1.5 (should be at baseline 0?)

    • r (U+0072): X=778.0,Y=1028.0 (should be at x-height 1026?)

    • 20 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments]

WARN: Are any segments inordinately short? (com.google.fonts/check/outline_short_segments)
  • WARN The following glyphs have segments which seem very short:

    • at (U+0040) contains a short segment B<<1226.0,436.0>-<1226.0,394.0>-<1245.0,372.0>>

    • at (U+0040) contains a short segment B<<1245.0,372.0>-<1264.0,350.0>-<1309.0,350.0>>

    • w (U+0077) contains a short segment B<<480.0,186.0>-<488.0,207.0>-<495.0,231.5>>

    • w (U+0077) contains a short segment B<<495.0,231.5>-<502.0,256.0>-<511.0,276.0>>

    • w (U+0077) contains a short segment B<<1190.0,286.0>-<1198.0,265.0>-<1205.0,238.5>>

    • y (U+0079) contains a short segment B<<269.0,1026.0>-<271.0,1021.0>-<287.5,986.0>>

    • braceleft (U+007B) contains a short segment L<<86.0,676.0>--<88.0,675.0>>

    • braceright (U+007D) contains a short segment L<<566.0,553.0>--<564.0,554.0>>

    • sterling (U+00A3) contains a short segment B<<296.0,832.0>-<295.0,840.0>-<294.5,847.0>>

    • sterling (U+00A3) contains a short segment B<<294.5,847.0>-<294.0,854.0>-<294.0,861.0>>

    • 36 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)
  • WARN The following glyphs have colinear vectors:

    • Eng (U+014A): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Eng (U+014A): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • M (U+004D): L<<1602.0,1251.0>--<1534.0,1096.0>> -> L<<1534.0,1096.0>--<1034.0,110.0>>

    • M (U+004D): L<<412.0,1456.0>--<887.0,526.0>> -> L<<887.0,526.0>--<973.0,322.0>>

    • M (U+004D): L<<973.0,322.0>--<1058.0,529.0>> -> L<<1058.0,529.0>--<1536.0,1456.0>>

    • N (U+004E): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • N (U+004E): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Nacute (U+0143): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Nacute (U+0143): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Ncaron (U+0147): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • 32 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-colinear-vectors]

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: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)
INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
  • INFO Hinting filesize impact:
ofl/mooli/Mooli-Regular.ttf
Dehinted Size 43.1kb
Hinted Size 60.8kb
Increase 17.8kb
Change 41.3 %
[code: size-impact]
INFO: EPAR table present in font? (com.google.fonts/check/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.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33]"
    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: Font contains all required tables? (com.google.fonts/check/required_tables)
  • INFO This font contains the following optional tables:

    • cvt

    • fpgm

    • loca

    • prep

    • GPOS

    • GSUB

    • gasp [code: optional-tables]

INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • INFO ofl/mooli [code: family-path]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 0 10 64 8 165 0
0% 0% 4% 26% 3% 67% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • PASS
  • DEBUG

…gftools[0.9.33] added

* Mooli Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] taken from the upstream repo https://github.com/googlefonts/mooliFont at commit googlefonts/mooliFont@ecf6cc6.
@emmamarichal
Copy link
Collaborator Author

Updated

Mooli: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added


9aa6938: [gftools-packager] Mooli: Version 1.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33] added

b43ad6d: description-metadata updated

@emmamarichal emmamarichal force-pushed the gftools_packager_ofl_mooli branch from eb7853b to b43ad6d Compare August 30, 2023 08:57
@emmamarichal emmamarichal removed the -- Needs Upstream Resolution Upstream fix required before moving forward label Aug 30, 2023
@github-actions
Copy link

FontBakery report

fontbakery version: 0.9.0a2

[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, 1 of them (100.00%) lack a STAT table.

    And these are the most common STAT axis orderings:
    [code: summary]


[17] Mooli-Regular.ttf
WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)
  • WARN OS/2 VendorID value 'NeWT' 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 for codepoints not covered by METADATA subsets. (com.google.fonts/check/metadata/unreachable_subsetting)
  • WARN The following codepoints supported by the font are not covered by
    any subsets defined in the font's metadata file, and will never
    be served. You can solve this by either manually adding additional
    subset declarations to METADATA.pb, or by editing the glyphset
    definitions.

  • U+02C7 CARON: try adding one of: yi, tifinagh, canadian-aboriginal

  • U+02D8 BREVE: try adding one of: yi, canadian-aboriginal

  • U+02D9 DOT ABOVE: try adding one of: yi, canadian-aboriginal

  • U+02DB OGONEK: try adding one of: yi, canadian-aboriginal

  • U+0302 COMBINING CIRCUMFLEX ACCENT: try adding one of: math, coptic, cherokee, tifinagh

  • U+0306 COMBINING BREVE: try adding one of: old-permic, tifinagh

  • U+0307 COMBINING DOT ABOVE: try adding one of: math, canadian-aboriginal, syriac, tai-le, tifinagh, coptic, old-permic, malayalam

  • U+030A COMBINING RING ABOVE: try adding syriac

  • U+030B COMBINING DOUBLE ACUTE ACCENT: try adding one of: osage, cherokee

  • U+030C COMBINING CARON: try adding one of: cherokee, tai-le
    18 more.

Use -F or --full-lists to disable shortening of long lists.

Or you can add the above codepoints to one of the subsets supported by the font: latin, latin-ext, menu [code: unreachable-subsetting]

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 + i

    • 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: 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 if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)
  • 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: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: Racute	Contours detected: 3	Expected: 2

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: fi	Contours detected: 2	Expected: 3

- Glyph name: uogonek	Contours detected: 2	Expected: 1

[code: contour-count]

WARN: Are there any misaligned on-curve points? (com.google.fonts/check/outline_alignment_miss)
  • WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:

    • S (U+0053): X=854.0,Y=1457.5 (should be at cap-height 1456?)

    • V (U+0056): X=581.0,Y=1.0 (should be at baseline 0?)

    • V (U+0056): X=767.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=654.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=441.0,Y=1.0 (should be at baseline 0?)

    • a (U+0061): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • b (U+0062): X=387.5,Y=0.5 (should be at baseline 0?)

    • g (U+0067): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • k (U+006B): X=177.0,Y=-1.5 (should be at baseline 0?)

    • r (U+0072): X=778.0,Y=1028.0 (should be at x-height 1026?)

    • 20 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments]

WARN: Are any segments inordinately short? (com.google.fonts/check/outline_short_segments)
  • WARN The following glyphs have segments which seem very short:

    • at (U+0040) contains a short segment B<<1226.0,436.0>-<1226.0,394.0>-<1245.0,372.0>>

    • at (U+0040) contains a short segment B<<1245.0,372.0>-<1264.0,350.0>-<1309.0,350.0>>

    • w (U+0077) contains a short segment B<<480.0,186.0>-<488.0,207.0>-<495.0,231.5>>

    • w (U+0077) contains a short segment B<<495.0,231.5>-<502.0,256.0>-<511.0,276.0>>

    • w (U+0077) contains a short segment B<<1190.0,286.0>-<1198.0,265.0>-<1205.0,238.5>>

    • y (U+0079) contains a short segment B<<269.0,1026.0>-<271.0,1021.0>-<287.5,986.0>>

    • braceleft (U+007B) contains a short segment L<<86.0,676.0>--<88.0,675.0>>

    • braceright (U+007D) contains a short segment L<<566.0,553.0>--<564.0,554.0>>

    • sterling (U+00A3) contains a short segment B<<296.0,832.0>-<295.0,840.0>-<294.5,847.0>>

    • sterling (U+00A3) contains a short segment B<<294.5,847.0>-<294.0,854.0>-<294.0,861.0>>

    • 36 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)
  • WARN The following glyphs have colinear vectors:

    • Eng (U+014A): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Eng (U+014A): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • M (U+004D): L<<1602.0,1251.0>--<1534.0,1096.0>> -> L<<1534.0,1096.0>--<1034.0,110.0>>

    • M (U+004D): L<<412.0,1456.0>--<887.0,526.0>> -> L<<887.0,526.0>--<973.0,322.0>>

    • M (U+004D): L<<973.0,322.0>--<1058.0,529.0>> -> L<<1058.0,529.0>--<1536.0,1456.0>>

    • N (U+004E): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • N (U+004E): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Nacute (U+0143): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Nacute (U+0143): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Ncaron (U+0147): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • 32 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-colinear-vectors]

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: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)
INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
  • INFO Hinting filesize impact:
ofl/mooli/Mooli-Regular.ttf
Dehinted Size 43.2kb
Hinted Size 61.1kb
Increase 18.0kb
Change 41.6 %
[code: size-impact]
INFO: EPAR table present in font? (com.google.fonts/check/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.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33]"
    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: Font contains all required tables? (com.google.fonts/check/required_tables)
  • INFO This font contains the following optional tables:

    • cvt

    • fpgm

    • loca

    • prep

    • GPOS

    • GSUB

    • gasp [code: optional-tables]

INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • INFO ofl/mooli [code: family-path]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 0 10 64 8 165 0
0% 0% 4% 26% 3% 67% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • PASS
  • DEBUG

@github-actions
Copy link

FontBakery report

fontbakery version: 0.9.0a2

[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, 1 of them (100.00%) lack a STAT table.

    And these are the most common STAT axis orderings:
    [code: summary]


[17] Mooli-Regular.ttf
🔥 FAIL: Check METADATA.pb parse correctly. (com.google.fonts/check/metadata/parses)
  • 🔥 FAIL Family metadata at ofl/mooli failed to parse.
    TRACEBACK:
    22:1 : Message type "google.fonts_public.FamilyProto" has no field named "stroke". [code: parsing-error]
WARN: Checking OS/2 achVendID. (com.google.fonts/check/vendor_id)
  • WARN OS/2 VendorID value 'NeWT' 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? (com.google.fonts/check/kerning_for_non_ligated_sequences)
  • WARN GPOS table lacks kerning info for the following non-ligated sequences:

    • f + i

    • 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: 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 if each glyph has the recommended amount of contours. (com.google.fonts/check/contour_count)
  • 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: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: Racute	Contours detected: 3	Expected: 2

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: uogonek	Contours detected: 2	Expected: 1

- Glyph name: Uogonek	Contours detected: 2	Expected: 1

- Glyph name: aogonek	Contours detected: 3	Expected: 2

- Glyph name: eogonek	Contours detected: 3	Expected: 2

- Glyph name: fi	Contours detected: 2	Expected: 3

- Glyph name: uogonek	Contours detected: 2	Expected: 1

[code: contour-count]

WARN: Are there any misaligned on-curve points? (com.google.fonts/check/outline_alignment_miss)
  • WARN The following glyphs have on-curve points which have potentially incorrect y coordinates:

    • S (U+0053): X=854.0,Y=1457.5 (should be at cap-height 1456?)

    • V (U+0056): X=581.0,Y=1.0 (should be at baseline 0?)

    • V (U+0056): X=767.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=654.0,Y=1.0 (should be at baseline 0?)

    • W (U+0057): X=441.0,Y=1.0 (should be at baseline 0?)

    • a (U+0061): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • b (U+0062): X=387.5,Y=0.5 (should be at baseline 0?)

    • g (U+0067): X=865.0,Y=1024.5 (should be at x-height 1026?)

    • k (U+006B): X=177.0,Y=-1.5 (should be at baseline 0?)

    • r (U+0072): X=778.0,Y=1028.0 (should be at x-height 1026?)

    • 20 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-misalignments]

WARN: Are any segments inordinately short? (com.google.fonts/check/outline_short_segments)
  • WARN The following glyphs have segments which seem very short:

    • at (U+0040) contains a short segment B<<1226.0,436.0>-<1226.0,394.0>-<1245.0,372.0>>

    • at (U+0040) contains a short segment B<<1245.0,372.0>-<1264.0,350.0>-<1309.0,350.0>>

    • w (U+0077) contains a short segment B<<480.0,186.0>-<488.0,207.0>-<495.0,231.5>>

    • w (U+0077) contains a short segment B<<495.0,231.5>-<502.0,256.0>-<511.0,276.0>>

    • w (U+0077) contains a short segment B<<1190.0,286.0>-<1198.0,265.0>-<1205.0,238.5>>

    • y (U+0079) contains a short segment B<<269.0,1026.0>-<271.0,1021.0>-<287.5,986.0>>

    • braceleft (U+007B) contains a short segment L<<86.0,676.0>--<88.0,675.0>>

    • braceright (U+007D) contains a short segment L<<566.0,553.0>--<564.0,554.0>>

    • sterling (U+00A3) contains a short segment B<<296.0,832.0>-<295.0,840.0>-<294.5,847.0>>

    • sterling (U+00A3) contains a short segment B<<294.5,847.0>-<294.0,854.0>-<294.0,861.0>>

    • 36 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-short-segments]

WARN: Do any segments have colinear vectors? (com.google.fonts/check/outline_colinear_vectors)
  • WARN The following glyphs have colinear vectors:

    • Eng (U+014A): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Eng (U+014A): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • M (U+004D): L<<1602.0,1251.0>--<1534.0,1096.0>> -> L<<1534.0,1096.0>--<1034.0,110.0>>

    • M (U+004D): L<<412.0,1456.0>--<887.0,526.0>> -> L<<887.0,526.0>--<973.0,322.0>>

    • M (U+004D): L<<973.0,322.0>--<1058.0,529.0>> -> L<<1058.0,529.0>--<1536.0,1456.0>>

    • N (U+004E): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • N (U+004E): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Nacute (U+0143): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • Nacute (U+0143): L<<380.0,1456.0>--<1147.0,342.0>> -> L<<1147.0,342.0>--<1225.0,215.0>>

    • Ncaron (U+0147): L<<1188.0,0.0>--<418.0,1113.0>> -> L<<418.0,1113.0>--<346.0,1237.0>>

    • 32 more.

Use -F or --full-lists to disable shortening of long lists. [code: found-colinear-vectors]

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: Does DESCRIPTION file contain a upstream Git repo URL? (com.google.fonts/check/description/git_url)
INFO: Show hinting filesize impact. (com.google.fonts/check/hinting_impact)
  • INFO Hinting filesize impact:
ofl/mooli/Mooli-Regular.ttf
Dehinted Size 43.2kb
Hinted Size 61.1kb
Increase 18.0kb
Change 41.6 %
[code: size-impact]
INFO: EPAR table present in font? (com.google.fonts/check/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.000; ttfautohint (v1.8.4.7-5d5b);gftools[0.9.33]"
    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: Font contains all required tables? (com.google.fonts/check/required_tables)
  • INFO This font contains the following optional tables:

    • cvt

    • fpgm

    • loca

    • prep

    • GPOS

    • GSUB

    • gasp [code: optional-tables]

INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • INFO ofl/mooli [code: family-path]

Summary

💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
0 1 9 108 8 121 0
0% 0% 4% 44% 3% 49% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • PASS
  • DEBUG

@RosaWagner RosaWagner merged commit 948422e into main Aug 30, 2023
@RosaWagner RosaWagner deleted the gftools_packager_ofl_mooli branch August 30, 2023 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Live
Development

Successfully merging this pull request may close these issues.

Add Mooli (Vernon Adams)
2 participants