perf: create junicode subset to improve performance #400
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As mentioned in #389, both font families (Junicode and Junicode-Italic) were over 1 MB in size but not heavily used on the site. To optimize this, I created subsets of both font families using glyphhanger and fonttools/pyftsubset. The subsets now contain only the characters that are actively being used.
This process resulted in the following size reductions:
Additionally, I disabled several unused OpenType features. The parameters used for pyftsubset were as follows:
--flavor=woff2 --layout-features='liga,kern' --no-hinting
You can view a comparison of the subset and the original font here. Some features would need to be enabled to maintain the font's appearance identical to the original. It's up to us to decide if it's worth it.
If you need to create new subsets, here are the relevant resources:
Glyphhanger repository
FontTools pyftsubset documentation