MK> I'm not sure exactly, what "next character has width 0" is good for.
If the next character is known as a combining character, it should be
overstruck. If it is known to be a control character, it should have
its usual effect. Otherwise, it may be dropped.
(Interesting question: is WO0 WO0 allowed?)
Application wants to send a Unicode control character that has just
been encoded yesterday; if the terminal emulator doesn't know about
it, this will f*ck up the cursor position. The application sends a WO0
to ensure that the cursor will end up at the right place.
Okay, I don't really care about this character. All I really want is
to avoid state.
Juliusz
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/linux-utf8/
