Re: term, utf-8 and cooked mode, combining characters

[Roland McGrath]

Seems pretty hairy.  Much easier to make you all use US-ASCII like God
intended. ;->

There is not just the question of backspace deleting a multibyte char,
there is also term's idea of the cursor location based on chars it has
emitted already.  Say there is a 4-byte char that occupies one physical
spot on the screen, followed by a tab in OXTABS mode.  term will
miscalculate how many spaces are needed to reach the tab stop.  There might
be other artifacts from this I am not thinking of at the moment.

I really don't think we want term to get a lot of fanciness about multibyte
characters from an implementation perspective.  I am not sure how to avoid
that if we want to have it behave more intelligently.