arakiken
Incorrect character set handling when designating 2-byte dscs
By designating g1 to dec technical with ESC ) > and then doing shift in (SI), I can output dec technical characters.
$ echo $'\033)>\016abcABC0\017'
αβχ∝∞÷⎬
This behavior is fine. However, if I designate g1 with SP >, I still get the same result.
$ echo $'\033) >\016abcABC0\017'
αβχ∝∞÷⎬
This behavior is problematic when displaying DRCS without unicode mapping.
Thank you. I'm very happy to receive your comment after such a long time. As you pointed out, there were some problems in the support for DRCS without using Unicode PUA. I took this opportunity to fix them. https://github.com/arakiken/mlterm/commit/d810b3d0ed47906c0119202e6dda77178cee6192
@arakiken Thank you, It looks the problem is fixed. DEL is rendered with zero width, but I believe that’s correct behavior when invoked via ISO-2022. (On my VT-330 as well, DEL in a 94-charset is ignored.)
The real issue is with the mapping spec: trying to place a 94-character set in the 0x20–0x7F range was unrealistic. I’ll bring a revised spec to the RLogin board soon—let’s discuss there.
Separately, the text cursor is quite hard to see over color DRCS, and nothing seems to change visually when selecting with the mouse, which is a bit painful. It would also be great if DRCS could be copy-pasted via Unicode.