On Mon, 4 Sep 2000, Bruno Haible wrote:
> Juliusz Chroboczek writes:
> > The cutbuffer mechanism is untyped, and it is deprecated.
>
> It is not untyped, it is always STRING (i.e. Latin1). Furthermore it
> is not deprecated; it is just "much simpler but much less powerful
> than the selection mechanism". See ICCCM spec section 3.
Ok, in that case the question is "how to make cutbuffers use UTF-8 in an
interoperable way?"
Possible solution -
Keep latin1 stuff in XA_CUT_BUFFER0, and define a new
XA_CUT_BUFFER0_UTF8.
Problem -
Old clients won't update/remove XA_CUT_BUFFER0_UTF8 when
they set XA_CUT_BUFFER0, so this would require server magic.
Is this solvable without evil server/client libs alterations?
--
Robert
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
