Skip to content

Comments

unifont: use sparse table, to be able to use codepoints after 0xFFFF#265

Merged
kdj0c merged 1 commit intokmscon:mainfrom
kdj0c:sparse_unifont
Jan 31, 2026
Merged

unifont: use sparse table, to be able to use codepoints after 0xFFFF#265
kdj0c merged 1 commit intokmscon:mainfrom
kdj0c:sparse_unifont

Conversation

@kdj0c
Copy link
Contributor

@kdj0c kdj0c commented Jan 29, 2026

Change the binary format of the unicode glyph. Add a block index, which allows to only store the glyph that are defined, and to store standard glyph more efficiently.
With this it's possible to add the unicode glyph that are beyond 0xffff
It also allows to save ~10% to the size of mod-unifont.so 2 228 792 bytes -> 1 994 264 bytes on x86_64

Change the binary format of the unicode glyph. Add a block index,
which allows to only store the glyph that are defined, and to store
standard glyph more efficiently.
With this it's possible to add the unicode glyph that are beyond
0xffff
It also allows to save ~10% to the size of mod-unifont.so
2 228 792 bytes -> 1 994 264 bytes on x86_64

Signed-off-by: Jocelyn Falempe <[email protected]>
@kdj0c kdj0c merged commit c64ffb9 into kmscon:main Jan 31, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant