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.

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

[VORG] >64k expansion #11

Open
behdad opened this issue Sep 14, 2021 · 1 comment
Open

[VORG] >64k expansion #11

behdad opened this issue Sep 14, 2021 · 1 comment

Comments

@behdad
Copy link
Member

behdad commented Sep 14, 2021

The length of the VORG table is determined from its major/minor version and the subsequent content. The only currently defined version 1.0 can only encode 16bit glyph indices. Here is how we expand the table's definition to encode glyph vertical origin for glyph indices beyond maxp.numGlyphs:

Basically, derive the length of the table from the version number and the table struct, then derive the excess bytes, then follow the same algorithm for deriving advance-width in the hmtx/vmtx expansion: #7 [We should move that to a named data-structure. Trimmed array?]

@behdad
Copy link
Member Author

behdad commented Mar 6, 2023

Speced: https://github.com/harfbuzz/boring-expansion-spec/blob/main/beyond-64k.md

NOT implemented in HarfBuzz.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant