googlefonts / googlefonts/fontations
Avar2 support in font identification and contour variations / situations where coords are provided
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 827
- Forks
- 76
- Avg merge
- 22h 33m
- Merged PRs (30d)
- 75
Description
In https://docs.rs/read-fonts/latest/read_fonts/tables/avar/type.Avar.html#method.version it says that Major version is set to 1.
1) For identification of avar2 fonts in Blink it would be useful if this API would be able to return 2 for avar2 fonts.
2) For applying axis variations and retrieving paths in Skrifa, `Glyph::draw`, and in situations where normalized coords are provided, Skrifa would need to know how to apply avar2 axes.
CC @behdad
Contributor guide
No contributing guide indexed for this repository
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 Avar version API described in the linked docs.rs page, then trace how Skrifa's Glyph::draw handles axis variations when normalized coordinates are provided. The work is done when avar2 fonts can be identified and avar2 axes are applied for the requested contour and path operations, with coverage for those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100