On 4 Sep 2000, Juliusz Chroboczek wrote:
> X has two distinct cut&paste mechanisms. The cutbuffer mechanism is
> untyped, and it is deprecated. The selection mechanism is typed and
> supports negociation.
Right.
> RB> But then xterm goes ahead and interprets the contents of the stuff
> RB> it put in the cut buffer as Latin1!
>
> As far as I know, XTerm first tries to get the selection. Only when
> there is no selection available will it attempt to use the cutbuffers.
This is what is happening :
1. Text selected (placed in selection, and cutbuffer)
2. Text deselected. Selection withdrawn. However, the text
in the cutbuffer is still available.
3. Paste. The UTF-8 string in the cutbuffer is incorrectly converted
via a latin1->utf8 converter.
> If this is not the case, it's a bug.
Perhaps the bug here is that the cutbuffer is not withdrawn at
the same time as the selection?
--
Robert
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
