linebender / linebender/skribo
Why provide Unicode functions in Rust rather than use Harfbuzz’s default?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 335
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Compare https://github.com/linebender/skribo/commit/51ed7899f0adeede2b79b14bc43167a0a8a00eb2 with https://github.com/harfbuzz/harfbuzz/blob/master/CONFIG.md#unicode-functions
> By default, HarfBuzz ships with its own compact subset of properties from Unicode Character Database that it needs. This is a highly-optimized implementation that depending on compile settings (optimize-size or not) takes around ~40kb or ~60kb. Using this implementation (default) is highly recommended, as HarfBuzz always ships with data from latest version of Unicode. This implementation can be disabled by defining `HB_NO_UCD`.
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 comparing skribo commit 51ed7899f0adeede2b79b14bc43167a0a8a00eb2 with HarfBuzz's CONFIG.md section on Unicode functions. Establish why Skribo provides its own Unicode implementation and whether the default HarfBuzz approach should replace it; done means documenting the rationale and agreeing on a concrete direction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100