Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[glyf1] Reset all other component axes to that of the font's #78

Closed
behdad opened this issue Dec 22, 2022 · 3 comments
Closed

[glyf1] Reset all other component axes to that of the font's #78

behdad opened this issue Dec 22, 2022 · 3 comments

Comments

@behdad
Copy link
Member

behdad commented Dec 22, 2022

I'm finding a great optimization opportunity if when setting a component's coordinates, we reset (set to 0) any unset coordinates, except for what has been set on the font as a whole. That is, NOT to carry forward the coordinates set on the current glyph. This matters a lot when various (unrelated) glyphs share the same axes.
@behdad
Copy link
Member Author

behdad commented Dec 22, 2022

@justvanrossum

@behdad
Copy link
Member Author

behdad commented Dec 22, 2022

This is such that I don't have to encode all the 0's.

@behdad
Copy link
Member Author

behdad commented Dec 22, 2022

This saves me 17% in the hanzi font I'm building. I'm going forward with this.

behdad added a commit that referenced this issue Dec 22, 2022
@behdad
[glyf1] Specify how coordinates are processed
fda8223 
Fixes #78
behdad added a commit to googlefonts/varc-rcjk that referenced this issue Dec 22, 2022
@behdad
Better coordinate encoding
9f752b5 
According to harfbuzz/boring-expansion-spec#78
davelab6 pushed a commit to googlefonts/varc-rcjk that referenced this issue Jan 27, 2023
@behdad @davelab6
Better coordinate encoding
3482bb0 
According to harfbuzz/boring-expansion-spec#78
davelab6 pushed a commit to googlefonts/varc-rcjk that referenced this issue Jan 27, 2023
@behdad
Better coordinate encoding
42c5922 
According to harfbuzz/boring-expansion-spec#78
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@behdad