typst brand yml: handle font families as possible lists#12542
Merged
gordonwoodhull merged 2 commits intomainfrom Apr 15, 2025
Merged
typst brand yml: handle font families as possible lists#12542gordonwoodhull merged 2 commits intomainfrom
gordonwoodhull merged 2 commits intomainfrom
Conversation
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
1 participant
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.
fixes #11933, allowing e.g.
Everywhere we read
brand.typography.*.familyin typst brand yml, treat it as a possible list and use the Typst CSSfont-familyconversion to Typst array.We should also consider expanding the brand yml schema to allow lists here, but commas are unambiguous in font names, as discussed in #11918 generic font families, so this is fairly safe.