`CoreTextSource` gives `Handle::Memory`, causing the path data to be lost, while `DirectWriteSource` and `FontconfigSource` all give `Handle::Path`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 840
- Forks
- 137
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 1
Description
See the function create_handles_from_core_text_collection in sources/core_text.rs. Is this intentional, e.g. for validating the font at query time to work around some CoreText peculiarity (just guessing)? Preserving the font path would be nice, anyway.
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 in sources/core_text.rs at create_handles_from_core_text_collection and compare how DirectWriteSource and FontconfigSource construct handles. Determine whether CoreText intentionally uses Handle::Memory; done means either preserving the font path consistently or documenting and testing the reason it cannot be preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100