Immediate-Mode-UI / Immediate-Mode-UI/Nuklear
Some fonts have incorrect glyph indexes
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 11.4k
- Forks
- 686
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 3
Description
Some fonts have incorrect glyph indexes because when a font fails to parse (maybe?) the glyph index is not increase, so the index is wrong
The above is a translation, sorry for my poor English
[https://github.com/Immediate-Mode-UI/Nuklear/blob/9486833f617c6c50d15f6040f184ca9f2c98c6ad/src/nuklear_font.c#L357](https://github.com/Immediate-Mode-UI/Nuklear/blob/9486833f617c6c50d15f6040f184ca9f2c98c6ad/src/nuklear_font.c#L357)
Here glyph_count is not increased
Contributor guide
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 at src/nuklear_font.c around line 357, where the issue reports that glyph_count is not increased when a font glyph fails to parse. Inspect the surrounding font parsing flow and reproduce the problem with an affected font if available. Done means glyph indexes remain correct even when a glyph cannot be parsed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100