Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fragment Mono : 1.010 added #5461

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
Merged
merged 4 commits into from
Oct 27, 2022
Merged

Fragment Mono : 1.010 added #5461

merged 4 commits into from
Oct 27, 2022

Conversation

@weiweihuanghuang
Copy link
Contributor

Fragment Mono

Fragment Mono is a monospaced coding version of Helvetica created by modifying and extending Nimbus Sans by URW Design Studio.

#5460

@RosaWagner RosaWagner linked an issue Oct 26, 2022 that may be closed by this pull request
Add Fragment Mono #5460
Closed
9 tasks
@RosaWagner
Copy link
Contributor

Fontbakery report

Fontbakery version: 0.8.10

[1] Family checks
ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

  • ℹ INFO From a total of 2 font files, 2 of them (100.00%) lack a STAT table.

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


[24] FragmentMono-Italic.ttf
💔 ERROR: Check small caps glyphs are available. (com.google.fonts/check/missing_small_caps_glyphs)
  • 💔 ERROR Failed with AttributeError: mapping
🔥 FAIL: Checking correctness of monospaced metadata. (com.google.fonts/check/monospace)
  • 🔥 FAIL The PANOSE numbers are incorrect for a monospaced font. Note: Family Type is set to 0, which does not seem right. [code: mono-bad-panose]
⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)
  • ⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]
⚠ WARN: Check copyright namerecords match license file. (com.google.fonts/check/name/license)
  • ⚠ 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)
  • ⚠ 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 For now we're still accepting http URLs, but you should consider using https instead.
    [code: http]
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API? (com.google.fonts/check/metadata/listed_on_gfonts)
  • ⚠ WARN Family not found via Google Fonts API. [code: not-found]
⚠ 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: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)
  • ⚠ WARN It seems that URW Design Studio is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]
⚠ 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: Glyph names are all valid? (com.google.fonts/check/valid_glyphnames)
  • ⚠ WARN The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit:
    semicolon_semicolon_semicolon.liga, less_numbersign_hyphen_hyphen.liga and asciitilde_asciitilde_greater.liga [code: legacy-long-names]
⚠ 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: Uogonek	Contours detected: 2	Expected: 1

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

- Glyph name: uni0E3F	Contours detected: 5	Expected: 3

- 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: uni0E3F	Contours detected: 5	Expected: 3 

- And 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:

    • dollar (U+0024): X=222.0,Y=2.0 (should be at baseline 0?)

    • dollar (U+0024): X=427.0,Y=698.0 (should be at cap-height 699?)

    • a (U+0061): X=419.5,Y=2.0 (should be at baseline 0?)

    • u (U+0075): X=130.0,Y=1.5 (should be at baseline 0?)

    • braceleft (U+007B): X=296.5,Y=1.0 (should be at baseline 0?)

    • braceright (U+007D): X=352.0,Y=698.0 (should be at cap-height 699?)

    • macron (U+00AF): X=265.0,Y=701.0 (should be at cap-height 699?)

    • macron (U+00AF): X=539.0,Y=701.0 (should be at cap-height 699?)

    • onequarter (U+00BC): X=220.0,Y=700.0 (should be at cap-height 699?)

    • onequarter (U+00BC): X=265.0,Y=700.0 (should be at cap-height 699?)

    • And 54 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:

    • dollar (U+0024) contains a short segment B<<368.0,704.0>-<370.0,704.0>-<371.0,704.0>>

    • ampersand (U+0026) contains a short segment L<<234.0,416.0>--<227.0,428.0>>

    • at (U+0040) contains a short segment B<<432.0,125.5>-<440.0,109.0>-<457.0,109.0>>

    • N (U+004E) contains a short segment L<<230.0,581.0>--<229.0,581.0>>

    • N (U+004E) contains a short segment L<<424.0,114.0>--<425.0,114.0>>

    • W (U+0057) contains a short segment L<<384.0,620.0>--<383.0,620.0>>

    • W (U+0057) contains a short segment L<<148.0,139.0>--<149.0,139.0>>

    • W (U+0057) contains a short segment L<<411.0,135.0>--<412.0,135.0>>

    • w (U+0077) contains a short segment L<<142.0,84.0>--<143.0,84.0>>

    • w (U+0077) contains a short segment L<<396.0,84.0>--<397.0,84.0>>

    • And 52 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+014B): L<<371.0,-37.0>--<379.0,0.0>> -> L<<379.0,0.0>--<456.0,363.0>>

    • And eng (U+014B): L<<542.0,376.0>--<462.0,0.0>> -> L<<462.0,0.0>--<449.0,-59.0>> [code: found-colinear-vectors]

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

  • ⚠ WARN The following glyphs have jaggy segments:

    • trademark (U+2122): L<<418.0,332.0>--<428.0,639.0>>/L<<428.0,639.0>--<363.0,332.0>> = 10.08883041066053

    • trademark (U+2122): L<<531.0,332.0>--<596.0,639.0>>/L<<596.0,639.0>--<477.0,332.0>> = 9.232951420697566

    • uni20A9 (U+20A9): L<<229.0,699.0>--<162.0,93.0>>/L<<162.0,93.0>--<360.0,699.0>> = 11.784848165590649

    • uni20A9 (U+20A9): L<<319.0,0.0>--<375.0,579.0>>/L<<375.0,579.0>--<187.0,0.0>> = 12.464119629827673

    • uni20A9 (U+20A9): L<<442.0,699.0>--<382.0,93.0>>/L<<382.0,93.0>--<573.0,699.0>> = 11.83946742345819

    • uni2116 (U+2116): L<<164.0,0.0>--<172.0,592.0>>/L<<172.0,592.0>--<45.0,0.0>> = 11.333755455975233

    • And uni2116 (U+2116): L<<222.0,699.0>--<216.0,102.0>>/L<<216.0,102.0>--<344.0,699.0>> = 11.525493565128695 [code: found-jaggy-segments]

ℹ 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:
/Users/rosalie/Desktop/fragment_mono_QA/fonts/ofl/fragmentmono/FragmentMono-Italic.ttf
Dehinted Size 79.8kb
Hinted Size 125.1kb
Increase 45.3kb
Change 56.7 %
[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.010; ttfautohint (v1.8.4.7-5d5b)"
    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: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)
  • ℹ INFO No sample_glyphs on METADATA.pb [code: no-samples]
ℹ 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

    • And gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • ℹ INFO /Users/rosalie/Desktop/fragment_mono_QA/fonts/ofl/fragmentmono [code: family-path]

[23] FragmentMono-Regular.ttf
💔 ERROR: Check small caps glyphs are available. (com.google.fonts/check/missing_small_caps_glyphs)
  • 💔 ERROR Failed with AttributeError: mapping
🔥 FAIL: Checking correctness of monospaced metadata. (com.google.fonts/check/monospace)
  • 🔥 FAIL The PANOSE numbers are incorrect for a monospaced font. Note: Family Type is set to 0, which does not seem right. [code: mono-bad-panose]
⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)
  • ⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]
⚠ WARN: Check copyright namerecords match license file. (com.google.fonts/check/name/license)
  • ⚠ 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)
  • ⚠ 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 For now we're still accepting http URLs, but you should consider using https instead.
    [code: http]
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API? (com.google.fonts/check/metadata/listed_on_gfonts)
  • ⚠ WARN Family not found via Google Fonts API. [code: not-found]
⚠ 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: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)
  • ⚠ WARN It seems that URW Design Studio is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]
⚠ 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: Glyph names are all valid? (com.google.fonts/check/valid_glyphnames)
  • ⚠ WARN The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit:
    semicolon_semicolon_semicolon.liga, less_numbersign_hyphen_hyphen.liga and asciitilde_asciitilde_greater.liga [code: legacy-long-names]
⚠ 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: Uogonek	Contours detected: 2	Expected: 1

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

- Glyph name: uni0E3F	Contours detected: 5	Expected: 3

- 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: uni0E3F	Contours detected: 5	Expected: 3 

- And 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:

    • a (U+0061): X=340.0,Y=0.5 (should be at baseline 0?)

    • h (U+0068): X=435.5,Y=523.5 (should be at x-height 524?)

    • n (U+006E): X=435.5,Y=523.5 (should be at x-height 524?)

    • p (U+0070): X=242.5,Y=0.5 (should be at baseline 0?)

    • q (U+0071): X=379.5,Y=1.5 (should be at baseline 0?)

    • t (U+0074): X=519.0,Y=-2.0 (should be at baseline 0?)

    • braceleft (U+007B): X=347.0,Y=699.5 (should be at cap-height 699?)

    • braceleft (U+007B): X=347.0,Y=-0.5 (should be at baseline 0?)

    • braceright (U+007D): X=271.0,Y=-0.5 (should be at baseline 0?)

    • braceright (U+007D): X=271.0,Y=699.5 (should be at cap-height 699?)

    • And 42 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:

    • ampersand (U+0026) contains a short segment L<<206.0,406.0>--<205.0,408.0>>

    • N (U+004E) contains a short segment L<<163.0,559.0>--<162.0,559.0>>

    • N (U+004E) contains a short segment L<<455.0,135.0>--<456.0,135.0>>

    • W (U+0057) contains a short segment L<<309.0,620.0>--<308.0,620.0>>

    • W (U+0057) contains a short segment L<<177.0,142.0>--<178.0,142.0>>

    • W (U+0057) contains a short segment L<<441.0,133.0>--<442.0,133.0>>

    • w (U+0077) contains a short segment L<<181.0,85.0>--<182.0,85.0>>

    • w (U+0077) contains a short segment L<<437.0,84.0>--<438.0,84.0>>

    • w (U+0077) contains a short segment L<<308.0,451.0>--<307.0,451.0>>

    • ordfeminine (U+00AA) contains a short segment B<<452.0,412.0>-<454.0,412.0>-<457.0,412.0>>

    • And 46 more.

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

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

  • ⚠ WARN The following glyphs have jaggy segments:

    • trademark (U+2122): L<<403.0,332.0>--<348.0,639.0>>/L<<348.0,639.0>--<348.0,332.0>> = 10.15696551936229

    • trademark (U+2122): L<<516.0,332.0>--<516.0,639.0>>/L<<516.0,639.0>--<462.0,332.0>> = 9.976036422751434

    • uni20A9 (U+20A9): L<<137.0,699.0>--<199.0,93.0>>/L<<199.0,93.0>--<268.0,699.0>> = 12.337420712236526

    • uni20A9 (U+20A9): L<<350.0,699.0>--<420.0,93.0>>/L<<420.0,93.0>--<481.0,699.0>> = 12.337157115263608

    • uni20A9 (U+20A9): L<<375.0,0.0>--<309.0,579.0>>/L<<309.0,579.0>--<243.0,0.0>> = 13.006111889763387

    • uni2116 (U+2116): L<<129.0,699.0>--<250.0,118.0>>/L<<250.0,118.0>--<250.0,699.0>> = 11.764350807103282

    • And uni2116 (U+2116): L<<220.0,0.0>--<102.0,576.0>>/L<<102.0,576.0>--<102.0,0.0>> = 11.577489206021184 [code: found-jaggy-segments]

ℹ 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:
/Users/rosalie/Desktop/fragment_mono_QA/fonts/ofl/fragmentmono/FragmentMono-Regular.ttf
Dehinted Size 77.7kb
Hinted Size 122.4kb
Increase 44.8kb
Change 57.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.010; ttfautohint (v1.8.4.7-5d5b)"
    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: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)
  • ℹ INFO No sample_glyphs on METADATA.pb [code: no-samples]
ℹ 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

    • And gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • ℹ INFO /Users/rosalie/Desktop/fragment_mono_QA/fonts/ofl/fragmentmono [code: family-path]

### Summary
💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
2 2 27 115 17 276 0
0% 0% 6% 26% 4% 63% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • PASS
  • DEBUG

QA_images.zip

@RosaWagner
Copy link
Contributor

Thanks @weiweihuanghuang looks very good.

I have a conflicted opinion about this fail:

🔥 FAIL: Checking correctness of monospaced metadata. (com.google.fonts/check/monospace)
🔥 FAIL The PANOSE numbers are incorrect for a monospaced font. Note: Family Type is set to 0, which does not seem right. [code: mono-bad-panose]

I understand you have plenty of ligatures and this parameter may force the double-width glyphs to appear single-width in some apps, is that correct? Do you think this check needs revision?

@weiweihuanghuang
Copy link
Contributor Author

Thanks for checking @RosaWagner!

Actually I ended up making all the ligature glyphs still conform to the monospaced advanced width but uses substitutions to add blank glyphs after the ligatures that are wider than 1 glyph which is what Fira Code and other coding fonts do.

Does the panose need to be set to 9 for monospace? I have it correctly set in the .glyphs file, did fontmake reset it all to 0?

@RosaWagner
Copy link
Contributor

Ah! Then it may not have been put where fontmake looks for it. I think that Fontmake is looking in the font instances custom parameters (and not font info). If this is what you did, then it is the other way around.

@weiweihuanghuang
Copy link
Contributor Author

Ohh ok that makes sense! I'll update my repo and add my latest files to the PR

@weiweihuanghuang
Copy link
Contributor Author

New fonts with correct PANOSE information added in e76d937

@RosaWagner
Copy link
Contributor

Did you run gftools add-font ofl/fragmentmono on your branch? If not, it would make sure metadata.pb is consistent with the font info.

@weiweihuanghuang
Copy link
Contributor Author

I did but I haven't run it again since.

@RosaWagner
Copy link
Contributor

Fontbakery report

Fontbakery version: 0.8.10

[1] Family checks
ℹ INFO: Check axis ordering on the STAT table. (com.google.fonts/check/STAT/axis_order)

  • ℹ INFO From a total of 2 font files, 2 of them (100.00%) lack a STAT table.

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


[23] FragmentMono-Italic.ttf
💔 ERROR: Check small caps glyphs are available. (com.google.fonts/check/missing_small_caps_glyphs)
  • 💔 ERROR Failed with AttributeError: mapping
⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)
  • ⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]
⚠ WARN: Check copyright namerecords match license file. (com.google.fonts/check/name/license)
  • ⚠ 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)
  • ⚠ 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 For now we're still accepting http URLs, but you should consider using https instead.
    [code: http]
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API? (com.google.fonts/check/metadata/listed_on_gfonts)
  • ⚠ WARN Family not found via Google Fonts API. [code: not-found]
⚠ 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: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)
  • ⚠ WARN It seems that URW Design Studio is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]
⚠ 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: Glyph names are all valid? (com.google.fonts/check/valid_glyphnames)
  • ⚠ WARN The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit:
    semicolon_semicolon_semicolon.liga, less_numbersign_hyphen_hyphen.liga and asciitilde_asciitilde_greater.liga [code: legacy-long-names]
⚠ 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: Uogonek	Contours detected: 2	Expected: 1

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

- Glyph name: uni0E3F	Contours detected: 5	Expected: 3

- 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: uni0E3F	Contours detected: 5	Expected: 3 

- And 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:

    • dollar (U+0024): X=222.0,Y=2.0 (should be at baseline 0?)

    • dollar (U+0024): X=427.0,Y=698.0 (should be at cap-height 699?)

    • a (U+0061): X=419.5,Y=2.0 (should be at baseline 0?)

    • u (U+0075): X=130.0,Y=1.5 (should be at baseline 0?)

    • braceleft (U+007B): X=296.5,Y=1.0 (should be at baseline 0?)

    • braceright (U+007D): X=352.0,Y=698.0 (should be at cap-height 699?)

    • macron (U+00AF): X=265.0,Y=701.0 (should be at cap-height 699?)

    • macron (U+00AF): X=539.0,Y=701.0 (should be at cap-height 699?)

    • onequarter (U+00BC): X=220.0,Y=700.0 (should be at cap-height 699?)

    • onequarter (U+00BC): X=265.0,Y=700.0 (should be at cap-height 699?)

    • And 54 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:

    • dollar (U+0024) contains a short segment B<<368.0,704.0>-<370.0,704.0>-<371.0,704.0>>

    • ampersand (U+0026) contains a short segment L<<234.0,416.0>--<227.0,428.0>>

    • at (U+0040) contains a short segment B<<432.0,125.5>-<440.0,109.0>-<457.0,109.0>>

    • N (U+004E) contains a short segment L<<230.0,581.0>--<229.0,581.0>>

    • N (U+004E) contains a short segment L<<424.0,114.0>--<425.0,114.0>>

    • W (U+0057) contains a short segment L<<384.0,620.0>--<383.0,620.0>>

    • W (U+0057) contains a short segment L<<148.0,139.0>--<149.0,139.0>>

    • W (U+0057) contains a short segment L<<411.0,135.0>--<412.0,135.0>>

    • w (U+0077) contains a short segment L<<142.0,84.0>--<143.0,84.0>>

    • w (U+0077) contains a short segment L<<396.0,84.0>--<397.0,84.0>>

    • And 52 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+014B): L<<371.0,-37.0>--<379.0,0.0>> -> L<<379.0,0.0>--<456.0,363.0>>

    • And eng (U+014B): L<<542.0,376.0>--<462.0,0.0>> -> L<<462.0,0.0>--<449.0,-59.0>> [code: found-colinear-vectors]

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

  • ⚠ WARN The following glyphs have jaggy segments:

    • trademark (U+2122): L<<418.0,332.0>--<428.0,639.0>>/L<<428.0,639.0>--<363.0,332.0>> = 10.08883041066053

    • trademark (U+2122): L<<531.0,332.0>--<596.0,639.0>>/L<<596.0,639.0>--<477.0,332.0>> = 9.232951420697566

    • uni20A9 (U+20A9): L<<229.0,699.0>--<162.0,93.0>>/L<<162.0,93.0>--<360.0,699.0>> = 11.784848165590649

    • uni20A9 (U+20A9): L<<319.0,0.0>--<375.0,579.0>>/L<<375.0,579.0>--<187.0,0.0>> = 12.464119629827673

    • uni20A9 (U+20A9): L<<442.0,699.0>--<382.0,93.0>>/L<<382.0,93.0>--<573.0,699.0>> = 11.83946742345819

    • uni2116 (U+2116): L<<164.0,0.0>--<172.0,592.0>>/L<<172.0,592.0>--<45.0,0.0>> = 11.333755455975233

    • And uni2116 (U+2116): L<<222.0,699.0>--<216.0,102.0>>/L<<216.0,102.0>--<344.0,699.0>> = 11.525493565128695 [code: found-jaggy-segments]

ℹ 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:
/Users/rosalie/Desktop/FragmentMono_Qa/fonts/ofl/fragmentmono/FragmentMono-Italic.ttf
Dehinted Size 79.8kb
Hinted Size 125.1kb
Increase 45.3kb
Change 56.7 %
[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.011; ttfautohint (v1.8.4.7-5d5b)"
    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: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)
  • ℹ INFO No sample_glyphs on METADATA.pb [code: no-samples]
ℹ 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

    • And gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • ℹ INFO /Users/rosalie/Desktop/FragmentMono_Qa/fonts/ofl/fragmentmono [code: family-path]

[22] FragmentMono-Regular.ttf
💔 ERROR: Check small caps glyphs are available. (com.google.fonts/check/missing_small_caps_glyphs)
  • 💔 ERROR Failed with AttributeError: mapping
⚠ WARN: DESCRIPTION.en_us.html should end in a linebreak. (com.google.fonts/check/description/eof_linebreak)
  • ⚠ WARN The last characther on DESCRIPTION.en_us.html is not a line-break. Please add it. [code: missing-eof-linebreak]
⚠ WARN: Check copyright namerecords match license file. (com.google.fonts/check/name/license)
  • ⚠ 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)
  • ⚠ 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 For now we're still accepting http URLs, but you should consider using https instead.
    [code: http]
⚠ WARN: METADATA.pb: Fontfamily is listed on Google Fonts API? (com.google.fonts/check/metadata/listed_on_gfonts)
  • ⚠ WARN Family not found via Google Fonts API. [code: not-found]
⚠ 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: METADATA.pb: Designers are listed correctly on the Google Fonts catalog? (com.google.fonts/check/metadata/designer_profiles)
  • ⚠ WARN It seems that URW Design Studio is still not listed on the designers catalog. Please submit a photo and a link to a webpage where people can learn more about the work of this designer/typefoundry. [code: profile-not-found]
⚠ 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: Glyph names are all valid? (com.google.fonts/check/valid_glyphnames)
  • ⚠ WARN The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit:
    semicolon_semicolon_semicolon.liga, less_numbersign_hyphen_hyphen.liga and asciitilde_asciitilde_greater.liga [code: legacy-long-names]
⚠ 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: Uogonek	Contours detected: 2	Expected: 1

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

- Glyph name: uni0E3F	Contours detected: 5	Expected: 3

- 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: uni0E3F	Contours detected: 5	Expected: 3 

- And 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:

    • a (U+0061): X=340.0,Y=0.5 (should be at baseline 0?)

    • h (U+0068): X=435.5,Y=523.5 (should be at x-height 524?)

    • n (U+006E): X=435.5,Y=523.5 (should be at x-height 524?)

    • p (U+0070): X=242.5,Y=0.5 (should be at baseline 0?)

    • q (U+0071): X=379.5,Y=1.5 (should be at baseline 0?)

    • t (U+0074): X=519.0,Y=-2.0 (should be at baseline 0?)

    • braceleft (U+007B): X=347.0,Y=699.5 (should be at cap-height 699?)

    • braceleft (U+007B): X=347.0,Y=-0.5 (should be at baseline 0?)

    • braceright (U+007D): X=271.0,Y=-0.5 (should be at baseline 0?)

    • braceright (U+007D): X=271.0,Y=699.5 (should be at cap-height 699?)

    • And 42 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:

    • ampersand (U+0026) contains a short segment L<<206.0,406.0>--<205.0,408.0>>

    • N (U+004E) contains a short segment L<<163.0,559.0>--<162.0,559.0>>

    • N (U+004E) contains a short segment L<<455.0,135.0>--<456.0,135.0>>

    • W (U+0057) contains a short segment L<<309.0,620.0>--<308.0,620.0>>

    • W (U+0057) contains a short segment L<<177.0,142.0>--<178.0,142.0>>

    • W (U+0057) contains a short segment L<<441.0,133.0>--<442.0,133.0>>

    • w (U+0077) contains a short segment L<<181.0,85.0>--<182.0,85.0>>

    • w (U+0077) contains a short segment L<<437.0,84.0>--<438.0,84.0>>

    • w (U+0077) contains a short segment L<<308.0,451.0>--<307.0,451.0>>

    • ordfeminine (U+00AA) contains a short segment B<<452.0,412.0>-<454.0,412.0>-<457.0,412.0>>

    • And 46 more.

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

⚠ WARN: Do outlines contain any jaggy segments? (com.google.fonts/check/outline_jaggy_segments)

  • ⚠ WARN The following glyphs have jaggy segments:

    • trademark (U+2122): L<<403.0,332.0>--<348.0,639.0>>/L<<348.0,639.0>--<348.0,332.0>> = 10.15696551936229

    • trademark (U+2122): L<<516.0,332.0>--<516.0,639.0>>/L<<516.0,639.0>--<462.0,332.0>> = 9.976036422751434

    • uni20A9 (U+20A9): L<<137.0,699.0>--<199.0,93.0>>/L<<199.0,93.0>--<268.0,699.0>> = 12.337420712236526

    • uni20A9 (U+20A9): L<<350.0,699.0>--<420.0,93.0>>/L<<420.0,93.0>--<481.0,699.0>> = 12.337157115263608

    • uni20A9 (U+20A9): L<<375.0,0.0>--<309.0,579.0>>/L<<309.0,579.0>--<243.0,0.0>> = 13.006111889763387

    • uni2116 (U+2116): L<<129.0,699.0>--<250.0,118.0>>/L<<250.0,118.0>--<250.0,699.0>> = 11.764350807103282

    • And uni2116 (U+2116): L<<220.0,0.0>--<102.0,576.0>>/L<<102.0,576.0>--<102.0,0.0>> = 11.577489206021184 [code: found-jaggy-segments]

ℹ 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:
/Users/rosalie/Desktop/FragmentMono_Qa/fonts/ofl/fragmentmono/FragmentMono-Regular.ttf
Dehinted Size 77.7kb
Hinted Size 122.4kb
Increase 44.8kb
Change 57.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.011; ttfautohint (v1.8.4.7-5d5b)"
    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: Check samples can be rendered. (com.google.fonts/check/metadata/can_render_samples)
  • ℹ INFO No sample_glyphs on METADATA.pb [code: no-samples]
ℹ 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

    • And gasp [code: optional-tables]

ℹ INFO: List all superfamily filepaths (com.google.fonts/check/superfamily/list)
  • ℹ INFO /Users/rosalie/Desktop/FragmentMono_Qa/fonts/ofl/fragmentmono [code: family-path]

### Summary
💔 ERROR 🔥 FAIL ⚠ WARN 💤 SKIP ℹ INFO 🍞 PASS 🔎 DEBUG
2 0 27 115 17 278 0
0% 0% 6% 26% 4% 63% 0%

Note: The following loglevels were omitted in this report:

  • SKIP
  • PASS
  • DEBUG

@RosaWagner RosaWagner merged commit 8db5a92 into google:main Oct 27, 2022
@weiweihuanghuang
Copy link
Contributor Author

Thank you! Can I ask how long it would take for it to show up on https://fonts.google.com/ ?

@RosaWagner
Copy link
Contributor

2 weeks in general, but it happened in the past that it took 2 month, so you have an idea ;)

@RosaWagner RosaWagner added --- Live Font is visible on API and removed --- to production labels Nov 11, 2022
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 I New Font

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Add Fragment Mono

2 participants

@weiweihuanghuang @RosaWagner