Split sources into a separate crate.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 840
- Forks
- 137
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 1
Description
Many users just want a crate for discovering fonts on the system, not rendering or any of the other stuff font-kit provides. It would be great to use font-kit, but there are concerns about it being very heavyweight as a dependency.
Would you consider splitting off the font discovery / sources, into a separate crate? It is very useful functionality on its own.
It seems like the font discovery crate could be made significantly more lightweight compared to font-kit proper.
There is some interest in using it in Bevy, see this issue.
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 by reviewing font-kit's existing font discovery and source functionality, then map which parts are independent of rendering and the other features. Define the boundary for a lighter standalone crate and verify that it still supports system font discovery without pulling in the full font-kit dependency set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100