Inconsistent font resolution: standalone vs fallback
Open
Nobody has claimed this yet.
text
- Dominant language
- Rust
- Stars
- 56.1k
- Forks
- 1.7k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 22
Description
Description
#let fa(c, font) = text(str.from-unicode(c), font: font)
#fa(0xf113, ("Libertinus Sans", "Font Awesome 6 Free"))
#fa(0xf113, ("Libertinus Sans", "Font Awesome 6 Brands"))
#fa(0xf113, "Font Awesome 6 Free")
I wouldn't say this is a bug because that glyph is indeed defined in Brands and not in Free, but it's strange that when using Free as the only font it's nevertheless found.
Reproduction URL
No response
Operating system
macOS
Typst version
- I am using the latest version of Typst
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Run the provided Typst snippet with the listed fonts and compare standalone font resolution with fallback resolution. Trace the two resolution paths and determine the intended consistent behavior. Done means the behavior is consistent and covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100