Owen Taylor wrote on 2000-09-04 22:54 UTC:
> > http://www.dcs.ed.ac.uk/home/jec/programs/xfsft/UTF8-selections.text
>
> - I disagree with the recommendations in the section of
> C0 and C1 control centers. (In particular the handling
> of \t, and treating a single LF as a soft linebreak.)
>
> Remember, most clients, when cutting and pasting, are cutting
> and pasting text provided by the user. The user expects
> C0/C1 characters to be passed across in the same way.
>
> So, this spec doesn't really need to describe handling
> in this much detail. In most circumstances, text provded
> by the user should be tranferred verbatim.
>
> If more detail is needed, then this spec should simply refer
> to the Unicode guidelines on newline handling.
I strongly agree with that!
If I cut and paste between say two Emacs instances where both sides have
UTF-8 buffers, I actually expect 100% guaranteed binary transparency of
the data transfer. If both partners in the transfer of a selection agree
to transfer UTF8_STRING and use UTF-8 as their locale representation
anyway (as I expect most UTF-8 upgraded X11 ASCII editors to do), then
the raw byte sequence should be transferred in the selection, without
any UTF-8 decoding involved. Special handling of control characters is
definitely not desirable in this case.
Markus
--
Markus G. Kuhn, Computer Laboratory, University of Cambridge, UK
Email: mkuhn at acm.org, WWW: <http://www.cl.cam.ac.uk/~mgk25/>
-
Linux-UTF8: i18n of Linux on all levels
Archive: http://mail.nl.linux.org/lists/
