aboutsummaryrefslogtreecommitdiff
path: root/composed.c
diff options
context:
space:
mode:
authorDaniel Eklöf <daniel@ekloef.se>2025-01-25 13:09:35 +0000
committerDaniel Eklöf <daniel@ekloef.se>2025-02-06 06:42:38 +0000
commit7a8d2b5e012636def9545075e01cdf9a6f309355 (patch)
tree2db0e0f122e12015ace0be700e702f76530e3429 /composed.c
parentgrid: reflow: handle composed characters longer than 2 cells (diff)
osc: wip: kitty text size protocol
This brings initial support for the new kitty text-sizing protocol. Note hat only the width-parameter ('w') is supported. That is, no font scaling, and no multi-line cells. For now, only explicit widths are supported. That is, w=0 does not yet work. There are a couple of changes to the renderer, to handle e.g. OSC 66 ; w=6 ; foobar ST There are two ways this can get rendered, depending on whether grapheme shaping has been enabled. We either shape it, and get an array of glyphs back that we render. Or, we rasterize each codepoint ourselves, and render each resulting glyph. The two cases ends up in two different renderer loops, that worked somewhat different. In particular, the first case has probably never been tested/used at all... With this patch, both are changed, and now uses some heuristic to differentiate between multi-cell text strings (like in the example above), or single-cell combining characters. The difference is mainly in which offset to use for the secondary glyphs. In a multi-cell string, each glyph is mapped to its own cell, while in the combining case, we try to map all glyphs to the same cell.
Diffstat (limited to 'composed.c')
0 files changed, 0 insertions, 0 deletions