update glyphsLib and unicodedata2 in requirements.txt#1758
Merged
Conversation
Member
|
We'll need to update icu4x now to match this, I imagine :) |
Member
|
does fonttools use the unicodedata2 package, or does it use the unicodedata module defined in fonttools? It doesn't look fontmake is using the unicode 17 data after applying this patch, or we'd see a bunch more new diffs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
a couple of updates that are relevant to us, among others:
glyphsLib 6.12.4 fixed duplicate postscript names for color layer glyphs (googlefonts/glyphsLib#1117)
unicodedata2 brings Unicode 17
JMM