-
Notifications
You must be signed in to change notification settings - Fork 71
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
Split vvar and hvar #151
Split vvar and hvar #151
Conversation
I do not remember why they weren't separate. Probably because Also, I would prefer to keep public API the same. |
If we keep them the same, how should we distinguish them from right side bearing / bottom side bearing then? Right now I haven't added a public API for them because we don't need them, but we might in the future, no? |
No, I don't mind the HVAR/VVAR split. I just want to keep the old naming for |
Honestly, I'm not sure how "right side bearing" offset should work to begin with. We do not have right/bottom side bearing to begin with. In any case, I suggest keeping public API unchanged. |
Not sure, all I know is that it's in the spec. :p
Got it, I'll change it back. |
Okay, so I changed back the function names in |
All good. Fix benches and we're done. |
Not sure why they were together before, as they have pretty different entries (maybe they added new ones?). But anyway, I had to split them up so that I can add support for variations in
y_origin
, and while I was at I also added the other fields that seem to be in the spec.See also
https://learn.microsoft.com/en-us/typography/opentype/spec/vvar
https://learn.microsoft.com/en-us/typography/opentype/spec/hvar