[screen-devel] [bug #32267] Latent bug in xterm mouse handling?

[Egmont Koblinger]

Follow-up Comment #2, bug #32267 (project screen):

> octal 233 = hex 9B occurs in many UTF-8 characters

For this reason, xterm refuses to recognize incoming C1 control codes in UTF-8
mode; see also
http://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h2-Control-Bytes_-Characters_-and-Sequences.

Some other terminal emulators, e.g. gnome-terminal and konsole recognize C1
codes in their UTF-8 representation, that is, C1 CSI is not the single byte
0x9B but rather U+009B encoded in UTF-8: 0xC2 0x9B.

I'm not sure what xterm does when it's not about recognizing incoming
sequences, but about generating them (keypresses and mouse events). We should
check what it does when it's asked to _generate_ C1 control codes. I'd guess
it also refuses that in UTF-8.

gnome-terminal doesn't have such an option of generating C1 sequences (neither
0x9B nor U+009B), and probably most other terminal emulators don't have it
either.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?32267>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/