Support for optional AAT font features
Open
Nobody has claimed this yet.
feature request
text
upstream
- Dominant language
- Rust
- Stars
- 56.1k
- Forks
- 1.7k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 22
Description
Description
How can we use the different stylistic sets in Zapfino to achieve the same result as in latex?
I have tried all combinations of true/false and integers
#text( font: "Zapfino", historical-ligatures: false, discretionary-ligatures: false, ligatures: false, stylistic-set: 2 ,[droog])
and the features
#text( font: "Zapfino", features: ("ss02", ) ,[droog])
but I always get the same result
Is this a bug?
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
Start with the Zapfino examples and feature settings in the issue, then compare the observed output with the LaTeX result. Investigate how optional AAT font features are represented and determine the expected behavior for the shown stylistic sets; done means the relevant feature settings produce the intended Zapfino variants.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- latex, macos, rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100