diff options
| author | Daniel Eklöf <daniel@ekloef.se> | 2020-05-01 09:52:40 +0000 |
|---|---|---|
| committer | Daniel Eklöf <daniel@ekloef.se> | 2020-05-01 09:52:40 +0000 |
| commit | cb5f80ec6a8bda1f71581261cc3fc56b20ebdd7d (patch) | |
| tree | a8762bda316e4b64e34d5b240f94dd06c7a5b891 /render.c | |
| parent | term: print: reset combining characters for this cell (diff) | |
vt: utf8: track combining characters that we failed to compose
When we detect a combining character, we first try to compose it with
the base character (like before).
When this fails, we instead add the combining character to the base
cell's combining characters array.
The reason for using a composed character when possible is twofold:
one, the rendered glyph will look better since it will be a single
glyph instead of two separate glyphs (possibly from different
fonts(!)). And two, for performance. A composed glyph is a single
glyph to render, while a decomposed glyph sequence means the renderer
has to render multiple glyphs for a single cell.
Diffstat (limited to 'render.c')
0 files changed, 0 insertions, 0 deletions
