samsa icon indicating copy to clipboard operation
samsa copied to clipboard

Issues to fix before TTFs are production-ready

Open Lorp opened this issue 5 years ago • 0 comments

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.

  • [x] glyph bounding boxes (simple glyphs)
  • [ ] glyph bounding boxes (composite glyphs)
  • [x] 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.

Lorp avatar May 11 '20 06:05 Lorp