Update ttf-parser, and long tail of RustyBuzz adjacent crates #82
Conversation
This file contains 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
...so that RustyBuzz can be updated in Typst without causing duplicates.
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I set out to make sure bumping the RustyBuzz dependency in Typst didn't break anything. It turns out hard to do without ending up with multiple versions of dependencies and conflicting types, but I think I have it all sorted now. This bump will need to be in a release to properly update the lock file, but I already have a working PoC using Git dependencies.
The catch is resvg is going to need a release too. I submitted a PR for that which is already merged, so now it's just a matter of waiting for a release.
When that is released this manifest can get a final tweak before merge to get rid of the Git dependency.