jerch
commented
1 month ago @Tyriar, @PerBothner, @christianparpart FYI - Yay, finally there is some movement on unicode side regarding terminals & proper unicode handling, see https://gist.github.com/XVilka/a0e49e1c65370ba11c17?permalink_comment_id=4615679#gistcomment-4615679
The initial write-up rightly lists common issues we see in our monospaced terminal world, but falls a bit short for prior art on the terminal (which is partially addressed by the second paper, but contains several flaws like referencing @egmontkob 's bidi algo wrongly and overall sounds quite biased). I wonder if we should get in contact to tell our side of the story & ideas? (I am somewhat hesitant here, those unicode topics are prone to conceptual headaches ...)
@Tyriar Seems the author of the first paper is a microsoft office dev - do you know if the window terminal devs are involved here as well?
Tyriar
WIP - For now this issue is meant as an aggregator for several issues and possible solutions we have around unicode in TEs.
In the long run we might have to settle certain aspects for TEs maybe ending up as something like a subspec, and/or define several sequences and behavioral pattern for TEs.
wcwidthand/or grapheme cluster widths, or undefined codepoints (e.g. PUA) - see https://github.com/xtermjs/xterm.js/issues/4813#issuecomment-1727399713 for a raw outline(Add more issues to the list...)