Skip to content

Conversation

@gordonwoodhull
Copy link
Contributor

fixes

Alternative PR to #13475.

A simpler approach, but one that diverges further from the Pandoc default.typst.

Process mainfont as if it sets brand.typography.base.family.

I think this is cleaner and safer, and doesn't have any questions of precedence.

But I'll sleep on it before merging this or the other one.

@posit-snyk-bot
Copy link
Collaborator

posit-snyk-bot commented Sep 30, 2025

🎉 Snyk checks have passed. No issues have been found so far.

security/snyk check is complete. No issues have been found. (View Details)

license/snyk check is complete. No issues have been found. (View Details)

@gordonwoodhull
Copy link
Contributor Author

I'm closing this in favor of #13475.

Despite this being a cleaner approach in terms of treating mainfont exactly the same as brand.typography.base.family, it is not as safe, and it's probably a good practice to keep logic in the templates where can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants