-
Notifications
You must be signed in to change notification settings - Fork 305
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
Google Fonts Onboarding #299
Comments
Hi @RosaWagner That would be me. |
Cool. So the idea would be to restructure the repo, re-export the fonts with Fontmake, while make sure they match google fonts spec in terms of metadata and glyphset (mostly).
|
We also need tot talk about the reserved font name… maybe a video call could be easier ? |
Ok. I planned to run test with Fontbakery on wednesday. I will fix as much as i can & probably will have questions, so i will be grateful if i can send them to you. I am comfortable with PR but i don't want to take advantage on your generosity. I would like to fix #286 before the release on Google Fonts. i believe this will be closed somewhere on this week. Video Call will be nice. We can schedule on wednesday. I'm available from 11am to 19am (UTC +3). |
Eheh I am UTC+2, so let's do video call around 4pm for you, 3pm for me. To what email address can I send you a hangout link ? (or you can send me any link to my email address on my website) To run fontbakery you will have to resolve the naming issue first: italic has "variable" in the family name, so FB doesn't recognise the font as the same family. Make sure the upright and the italic share the same family name. |
Ok, it's settled then [email protected] Ok, will correct that. |
Thank you both! Really nice to see your active maintenance @philippnurullin :D |
Hello, as you probably know, a lot of people are interested in using this font through Google Fonts platform: google/fonts#2308. I am in charge of preparing it in order to add it to the catalogue. Who can I contact to talk about the process ?
The text was updated successfully, but these errors were encountered: