googlefonts / googlefonts/ufo2ft

Caching unchanged tables or glyphs

Open
#321 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
176
Forks
48
PR merge metrics
No merged PRs in 30d

Description

It's possible that a user constantly generates a font while they're developing or designing it and if a UFO file gets larger compiling could get slower. Since there are ways to track which parts of a UFO is changed I was wondering if this could be something to consider for future if ufo2ft could cache some parts inside the UFO like what makeOtf does (it saves the post-processed outlines inside another layer inside the UFO)? This will save a lot of time for developing fonts. Also if features are not changed and only an outline is changed; there is no reason to write all the features maybe? I know it's kinda invasive and huge modification but it also improves the design/development process dramatically.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.