Open Vzolive opened 8 months ago
If I've done anything wrong please let me know so I can correct the submission, I believe everything is in accordance with the requirements
The font source files are called Rubik which is strange.
Hello @Vzolive, Thank you for the submission. Unfortunately, some glyphs are missing. I invite you to check the Google Fonts guide in order to improve it: https://googlefonts.github.io/gf-guide/index
Feel free to ask if you have any questions!
@emmamarichal Thanks for the feedback, i'm gonna update those, if you have any other thing that needs to add/change please let me know
@emmamarichal I've added the new glyphs, I think I've managed to add them all, could you kindly check if I've missed any? if so, I'll make the adjustments now
These glyphs are still missing: Scommaaccent Germandbls Tcommaaccent idotaccent jdotless scommaaccent tcommaaccent nbspace ellipsis periodcentered.loclCAT periodcentered.loclCAT.case emdash quotesinglbase guilsinglleft guilsinglright trademark minus dieresiscomb dotaccentcomb gravecomb acutecomb hungarumlautcomb caroncomb.alt circumflexcomb caroncomb brevecomb ringcomb tildecomb macroncomb commaaccentcomb cedillacomb ogonekcomb dotaccent ring ogonek
But let me check with the team if we accept the project, before asking you to add all of this :) I'll let you know! Thank you for your patience.
thanks @emmamarichal, i'll wait for your confirmation, if you give me the ok i'll add the missing glyphs
@Vzolive thanks for submitting this and thanks @emmamarichal for an initial review.
Overall I like the design but I do find some issues with the submission that mean I am not yet ready to accept it.
Most importantly, the design itself has some peculiar choices - /i and /j are different heights, /!/? and the quote marks are very tall, the crossbar on the /T and /t are illegible, the crossbar on /f is peculiarly low (and perhaps its head is a little short), lack of overshoot on the /o especially but also /O and others. I would be happy to connect you with a senior type designer to give you a tutorial on these issues so you can improve the design.
There are also some important metadata issues: First, the family name is Zoika Bold
but I would like to propose it a Zoika One
since it is a single style design, yet it is easy to imagine a full range of weights, so an initial single-style release would be good to do, yet without taking up the Zoika
family name all for itself. There are likely others as Emma has pointed out.
Finally, I also noticed that you've posted only a UFO source file in your repo, but the fontinfo.plist reveals that you made it with Fontlab, and we require the VFB/VFC file posted as that is the actual sources you use to maintain the project.
I look forward to hearing from you and seeing your updates, I think this project has strong potential :) I'm moving to the Icebox for now. If you are waiting to hear from Google Fonts, please do email fonts@google.com to follow up.
Font Project Git Repo URL: (https://github.com/Vzolive/Zoika-bold/tree/main)
Super short description of the Font Family:
Zoika bold is a Display Font, classy and luxury bold font with a unique personality. It includes uppercase, lowercase, number, symbols and support multilingual.
Zoika looks great for logos, labels, magazine or book cover, website header, flyer, clothing, photography, branding, prints, headline, typography poster, product packaging, or event your wedding invitation.
Requirements:
Google Fonts will publish only fonts that match its requirements. Please familiarize yourself with the complete documentation in the Google Fonts Guide (GF-Guide) and ensure your font project complies with them before submitting the font family. You can also use the Google Fonts Project Template, which will help you create a repository that follows the needed structure and includes build requirements.
By filling this issue, you can confirm the project meets the requirements (by ticking the cases or putting x between the square brackets in text mode):