redstonedesign
commented
3 days ago hey @emmamarichal , are you able to advise if we need to do anything else to get this added as a new font?
Open redstonedesign opened 1 week ago
redstonedesign
commented
3 days ago hey @emmamarichal , are you able to advise if we need to do anything else to get this added as a new font?
m4rc1e
commented
3 days ago Hey @redstonedesign.
Thank you for the submission. I will raise it in our onboarding meeting this week. I'll post back whether or not we accept the family (looks decent so it's likely).
Please be aware that onboarding the family may take some time and we may require further work in order for it to meet our criteria.
davelab6
commented
3 days ago This is wonderful work! Thanks @redstonedesign :)
I've marked this as accepted but I believe it may not happen until mid Q1. hope thats OK for you
emmamarichal
commented
2 days ago Hi @redstonedesign!
Thank you for this great submission! I took a quick look so you can be able to add some changes before Q1 :)
/.notdef/periodcentered.loclCAT/periodcentered.loclCAT.case/caroncomb.alt/idotaccent
Remark: the .notdef needs to contain outlines (a rectangle would be the best solution)Variable font When I will export the fonts, I'll generate a variable, this is the format we prefer. Nothing to do on your side, I just let you know.
Interpolation issues
There is a interpolation issue with the eogonek.
-Kerning There is no kerning at all, it would be great if you could add the main pairs :) Please let me know if you need some kerning proofs!
fontbakery version: 0.13.0a0
Expected "Parkinsans[wght].ttf. Got Parkinsans_AW_Google[wght].ttf.
[code: bad-filename]GPOS table lacks kerning information.
[code: lacks-kern-info]Lcaron is decomposed and therefore could not be checked. Please check manually.
[code: decomposed-outline] * ⚠️ **WARN**dcaron is decomposed and therefore could not be checked. Please check manually.
[code: decomposed-outline] * ⚠️ **WARN**lcaron is decomposed and therefore could not be checked. Please check manually.
[code: decomposed-outline] * ⚠️ **WARN**tcaron is decomposed and therefore could not be checked. Please check manually.
[code: decomposed-outline]Interpolation issues were found in the font:
- Contour 1 start point differs in glyph 'eogonek' between location wght=475 and location wght=800
- Contour 1 in glyph 'eogonek': becomes underweight between wght=475 and wght=800.
- Contour 1 point 14 in glyph 'eogonek' has a kink between location wght=475 and location wght=800
This font lacks caret position values for ligature glyphs on its GDEF table.
[code: lacks-caret-pos]The most common width is 476 among a set of 2 math glyphs. The following math glyphs have a different width, though:
Width = 655: plus
Width = 504: less
Width = 676: equal
Width = 492: greater
Width = 651: logicalnot
Width = 657: plusminus
Width = 591: multiply
Width = 637: divide
Width = 519: minus
Width = 487: approxequal
Width = 664: notequal
[code: width-outliers]The following glyphs could not be reached by codepoint or substitution rules:
- indianrupee
- turkishlira
Family metadata at . does not have an article.
[code: lacks-article]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.
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
No dotted circle glyph present
[code: missing-dotted-circle]The dot of soft dotted characters used in orthographies must disappear in the following strings: i̊ i̋ j̀ j́ j̃ j̄ j̈ į̀ į́ į̂ į̃ į̄ į̌
The dot of soft dotted characters should disappear in other cases, for example: i̇ ǐ i̦̇ i̦̊ i̦̋ ǐ̦ i̧̇ i̧̊ i̧̋ ǐ̧ ĵ j̆ j̇ j̊ j̋ ǰ j̦̀ j̦́ ĵ̦ j̦̃
Your font fully covers the following languages that require the soft-dotted feature: Lithuanian (Latn, 2,357,094 speakers), Dutch (Latn, 31,709,104 speakers).
Your font does not cover the following languages that require the soft-dotted feature: Ekpeye (Latn, 226,000 speakers), Mundani (Latn, 34,000 speakers), Mfumte (Latn, 79,000 speakers), Zapotec (Latn, 490,000 speakers), Gulay (Latn, 250,478 speakers), Dii (Latn, 71,000 speakers), Koonzime (Latn, 40,000 speakers), Vute (Latn, 21,000 speakers), Ma’di (Latn, 584,000 speakers), Dan (Latn, 1,099,244 speakers), Navajo (Latn, 166,319 speakers), Bete-Bendi (Latn, 100,000 speakers), Southern Kisi (Latn, 360,000 speakers), Ijo, Southeast (Latn, 2,471,000 speakers), Nateni (Latn, 100,000 speakers), Yala (Latn, 200,000 speakers), Belarusian (Cyrl, 10,064,517 speakers), Basaa (Latn, 332,940 speakers), Mango (Latn, 77,000 speakers), Nzakara (Latn, 50,000 speakers), South Central Banda (Latn, 244,000 speakers), Bafut (Latn, 158,146 speakers), Igbo (Latn, 27,823,640 speakers), Fur (Latn, 1,230,163 speakers), Ngbaka (Latn, 1,020,000 speakers), Cicipu (Latn, 44,000 speakers), Makaa (Latn, 221,000 speakers), Lugbara (Latn, 2,200,000 speakers), Aghem (Latn, 38,843 speakers), Kpelle, Guinea (Latn, 622,000 speakers), Ebira (Latn, 2,200,000 speakers), Ukrainian (Cyrl, 29,273,587 speakers), Kom (Latn, 360,685 speakers), Avokaya (Latn, 100,000 speakers), Sar (Latn, 500,000 speakers), Ejagham (Latn, 120,000 speakers).
[code: soft-dotted]The following glyphs have on-curve points which have potentially incorrect y coordinates:
* Iogonek (U+012E): X=202.0,Y=1.0 (should be at baseline 0?)
* Lcaron (U+013D): X=273.5,Y=689.0 (should be at cap-height 690?)
* W (U+0057): X=220.0,Y=-1.0 (should be at baseline 0?)
* Wacute (U+1E82): X=220.0,Y=-1.0 (should be at baseline 0?)
* Wcircumflex (U+0174): X=220.0,Y=-1.0 (should be at baseline 0?)
* Wdieresis (U+1E84): X=220.0,Y=-1.0 (should be at baseline 0?)
* Wgrave (U+1E80): X=220.0,Y=-1.0 (should be at baseline 0?)
* acircumflex (U+00E2): X=338.0,Y=688.0 (should be at cap-height 690?)
* cdotaccent (U+010B): X=275.5,Y=691.5 (should be at cap-height 690?)
* cdotaccent (U+010B): X=340.5,Y=691.5 (should be at cap-height 690?)
* 30 more.
Use -F or --full-lists to disable shortening of long lists.
[code: found-misalignments]The following glyphs have a counter-clockwise outer contour:
* turkishlira has a counter-clockwise outer contour
* turkishlira has a counter-clockwise outer contour
* turkishlira has a counter-clockwise outer contour
This font file does not have a 'meta' table.
[code: lacks-meta-table]OS/2 VendorID value 'NONE' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx
[code: unknown]Hinting filesize impact:
| Parkinsans_AW_Google[wght].ttf | |
|---|---|
| Dehinted Size | 76.8kb |
| Hinted Size | 76.8kb |
| Increase | 24 bytes |
| Change | 0.0 % |
This font contains the following optional tables:
- loca
- prep
- GPOS
- GSUB
- gasp
This font doesn't have an ARTICLE.en_us.html file.
[code: missing-article]EPAR table not present in font. To learn more see https://github.com/fonttools/fontbakery/issues/818
[code: lacks-EPAR]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]Could not detect which version of ttfautohint was used in this font. It is typically specified as a comment in the font version entries of the 'name' table. Such font version strings are currently: ['Version 1.000']
[code: version-not-detected]| 💥 ERROR | ☠ FATAL | 🔥 FAIL | ⚠️ WARN | ⏩ SKIP | ℹ️ INFO | ✅ PASS | 🔎 DEBUG |
|---|---|---|---|---|---|---|---|
| 0 | 0 | 1 | 14 | 100 | 8 | 129 | 0 |
| 0% | 0% | 0% | 6% | 40% | 3% | 51% | 0% |
Note: The following loglevels were omitted in this report:
redstonedesign
commented
2 days ago Thanks @m4rc1e, @davelab6 and @emmamarichal for the kind feedback!
We appreciate the swift review, we’ll get started on fixing these issues today.
If there’s anything we can do to speed up the onboarding process to get the font live sooner it would be hugely appreciated! Parkinson's UK (the UK's leading charity for the condition) are launching their new brand at the start of 2025. The charity largely relies on people with Parkinson's in local communities to create and share comms, anything we can do to get them set up in 2024, ahead of launch, would be super amazing. :pray:
redstonedesign
commented
2 days ago Hey @emmamarichal, if you do have some recommended kerning proofs that we could use that’d be super helpful!
vv-monsalve
commented
2 days ago HI @redstonedesign Then there is the Octopus tool you can get familiar with, but particularly its sample text strings could be of great help for an extended revision.
emmamarichal
commented
1 day ago Hi @redstonedesign, Here you can find some tools for checking at least the basic kerning :)
You can also find a lot of ressources here: https://typedesignresources.com/#proofing-tools
When we do the fonts QA, we use the gftools qa templates. You can also refer to these text strings: Spacing-kerning_checks.zip
Font Project Git Repo URL:
https://github.com/redstonedesign/parkinsans
Description:
Parkinsans is a geometric sans serif designed for UK charity Parkinson’s UK. Energetic, human, accessible, approachable – Parkinsans embodies Parkinson’s UK’s relentless energy, whilst typographic quirks reflect the unique experience of every Parkinson’s journey. Consisting of 6 weights, Parkinsans is designed to grab attention at display sizes and provide an accessible, easy reading experience for short form copy. Designed by award-winning, London based creative agency Red Stone, Parkinsans is derived from Indian Type Foundry's Poppins.
Requirements:
By opening this issue, I confirm the project meets the following requirements:
[x] The entire font project is available in a Github repository (repo) and licensed under the OFL
[x] The source files are available in the repo
[x] I am the sole copyright author of the entire project, or, all other copyright authors have licensed their work to me under the OFL
[x] There are no "Reserved Font Names" in the OFL license information, or in the project documentation of any known upstream projects. If there are RFNs, they are not used in whole or in part in this family name, or, I want to discuss how Google can work with my use of them.
[x] The family name is unique according to namecheck.fontdata.com
[x] The font supports at least the Google Fonts 'Latin Core' glyphset from github.com/googlefonts/glyphsets (direct link)
[x] The repo has the Google Fonts preferred upstream repo structure
[x] I have read, agree with, and comply with, the full Google Fonts contributing requirements
[x] I will maintain the repository and participate in the onboarding process (addressing, solving, and responding to issues, merging pull requests, etc)
Image: