On Mon, 4 Sep 2000, Robert Brady wrote:
> > 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.
>
> I think this can be reproduced as follows -
> double left click on a UTF-8 word
> single left click
> single middle click
> note mangled string that has been pasted
>
> This appears to be an ancient bug, (I can reproduce it as far back as
> xterm-121). I'll try to track it down...
The following comment from button.c, sheds some light on the issue.
/* Cutbuffers are untyped, so in the wide chars case, we
just store the raw UTF-8 data. It is unlikely it
will be useful to anyone. */
But then xterm goes ahead and interprets the contents of the stuff it put
in the cut buffer as Latin1!
I can't see a good way of fixing this, and keeping it so you can
cut text from a Latin1 application and it ends up right in a
UTF-8 one. Anyone know if this has already been solved?
--
Robert
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
