-
Notifications
You must be signed in to change notification settings - Fork 191
Closed
Description
Hello,
I've been commissioned to onboard Vazir to Google Fonts.
We’re interested only in the Variable Font TTF. The rest will be generated from that by Google engineers on their servers.
I’m wondering how to proceed practically: Whether to fork the repo and apply the changes required by our specifications or whether to PR the changes back to you.
As far as I can tell at the moment, the changes would be:
- Copyright field in name table change to
Copyright 2015 The Vazir Project Authors (https://github.com/rastikerdar/vazir-font)
- Eliminate nested components
- Instance weight values
300
,500
, and700
instead of250.0
,566.6665954589844
, and733.3332977294922
(See https://github.com/googlefonts/gf-docs/tree/main/Spec#axes) - Bit 3 of the
head
table needs to be set for PPEM rounding, since this is a hinted font - Add
STAT
andavar
tables OS/2.fsSelection
bit 7 needs to be set (Use Typo metrics)- Adjustments to vertical metrics (
OS/2.usWinDescent
to1116
instead of1100
) - Decompose transformed components
Since Vazir seems to be a very popular font available for a multitude of environments, please let me know whether you are comfortable with the proposed changes to your repo or not.
Thank you.
gitArashahmaduxui, sepehrbrj, cerpinn, mparvazi, bateni and 14 more
Metadata
Metadata
Assignees
Labels
No labels