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

Issues to fix before TTFs are production-ready #37

Open
2 of 9 tasks
Lorp opened this issue May 11, 2020 · 0 comments
Open
2 of 9 tasks

Issues to fix before TTFs are production-ready #37

Lorp opened this issue May 11, 2020 · 0 comments

Comments

@Lorp
Copy link
Owner

Lorp commented May 11, 2020

This issue tracks what needs to be fixed in exported static TTFs before they can be used for production. Fixed subissues are marked as checked. New subissues may be added to the list.

  • glyph bounding boxes (simple glyphs)
  • glyph bounding boxes (composite glyphs)
  • head.modified date
  • table checksums
  • GSUB table (includes rvrn feature variations)
  • GPOS table (instantiate kerning)
  • MVAR table (instantiate OS/2 table and other font-wide metrics)
  • cvar table (instantiatecvt table, turns variable hinting into static hinting)
  • font bounding box (in head table)

Note: The static TTF instances generated by Samsa-GUI and Samsa-CLI both use the SamsaFont.exportInstance() method in samsa-core.js, so binaries are identical.

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

No branches or pull requests

1 participant