googlefonts / googlefonts/fontations
What's fontations' WASM story?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 827
- Forks
- 76
- Avg merge
- 22h 33m
- Merged PRs (30d)
- 75
Description
I ask because I find [opentype.js](https://www.npmjs.com/package/opentype.js) and [fontkit](https://www.npmjs.com/package/fontkit) lacking in subsetting variable fonts compared to harfbuzz/Klippa.
Klippa works without any code changes with wasm32-wasip2 but needs code changes to target wasm32-unknown-unknown.
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
The issue names no files, tests, or entry points. Start by clarifying the intended WASM targets and the differences between wasm32-wasip2 and wasm32-unknown-unknown described in the issue. Done should mean a documented, agreed-upon WASM support story for fontations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust, wasm
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100