Hello,
: Previous versions of XTerm were unable to show combining characters
: actually attached to doublewidth characters. The attached patch
: (against #144) should rectify this.
OK, they display now, but still with the bug that they vanish when the
cursor moves over their position.
Also, the illegal character FFFF is now displayed in double width although
it's not considered double-width by the wide-spread function "iswide".
(I can't check the Unicode data base because the downloadable file seems
to be corrupted within the line for FF5D.)
Also I'd like to attach the following bug comments which are related to UTF-8
and may or may not be related to the double-width patch.
Kind regards,
Thomas Wolff
-----------------------------------------------------------------------------
Crashes (additional information)
The xterm crashes I reported also occur with very small files and with
some of them only sometimes. The common thing seems to be a number of
NUL characters in between regular text.
-----------------------------------------------------------------------------
Auto wraparound (bug report withdrawn)
I had reported that auto wraparound would not work in UTF-8 mode on
the command line. I had not noticed that this only happens if non-ASCII
characters are entered on the command line and the problem seems to be
wrap-around handling by bash or getline; apparently it emits a blank and
a CR when it thinks it's at the end of the line, probably in order to
support various terminal handling modes.
(I had always tested this by quickly entering a sequence of junk
characters from the base line of the keyboard - which includes an 'ö'
on a German keyboard - so my test strategy was not good.)
-----------------------------------------------------------------------------
xterm copy and paste
Character set interpretation of the paste buffer seems to be unstable.
If I copy a string like "aäx" and paste it several times, I get the same
string "aäx" once or a few times, then "aäx" instead.
-----------------------------------------------------------------------------
Special keys (you certainly know...)
Dead keys and the compose-key don't work yet in UTF-8 mode.
-----------------------------------------------------------------------------
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
