Groups | Search | Server Info | Login | Register

Groups > comp.emacs > #2532

Re: Fixing Garbled Encodings

From Aidan Kehoe <kehoea@parhasard.net>
Newsgroups comp.emacs, comp.emacs.xemacs
Subject Re: Fixing Garbled Encodings
Followup-To comp.emacs.xemacs
Date 2026-02-26 21:24 +0000
Message-ID <875x7jw64r.fsf@parhasard.net> (permalink)
References (6 earlier) <87ldgiwr02.fsf@parhasard.net> <10nl1du$6bih$1@dont-email.me> <877bs1g2yv.fsf@home.hst.name> <10nldkn$atq5$4@dont-email.me> <87a4wvo6vg.fsf@home.hst.name>

Cross-posted to 2 groups.

Followups directed to: comp.emacs.xemacs

Show all headers | View raw

 Ar an séú lá is fiche de mí Feabhra, scríobh Henry S. Thompson: 

 > [...] I would note that there are at least two ways to get a string that
 > appears in an (x)emacs buffer running python sent to an (x)emacs function as
 > an argument:
 > 
 >   1) Copy it with a sweep of the mouse in the python buffer and paste
 >      it with a middle-button-click into *scratch";
 > 
 >   2) Select and and copy it with the keyboard (e.g. C-space, M-f, M-w)
 >      and paste it with C-y.
 > 
 > Those two give _different_ results for me in XEmacs, but that's
 > probably off-topic for your question.

The second is the more authoritative given there’s no need for the text to be
switched between the XEmacs internal encoding and the clipboard encoding (which
cannot represent things like “this was an isolated ?\80 encountered when
decoding UTF-8” or, often, “this is a code point in JISX0208 which has no
Unicode representation.”

-- 
‘As I sat looking up at the Guinness ad, I could never figure out /
How your man stayed up on the surfboard after fourteen pints of stout’
(C. Moore)

Back to comp.emacs | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-15 05:48 +0000
  Re: Fixing Garbled Encodings Julian Bradfield <jcb@inf.ed.ac.uk> - 2026-02-16 10:11 +0000
    Re: Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-16 20:35 +0000
    Re: Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-17 03:52 +0000
      Re: Fixing Garbled Encodings Julian Bradfield <jcb@inf.ed.ac.uk> - 2026-02-17 15:42 +0000
        Re: Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-24 01:55 +0000
          Re: Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-24 04:41 +0000
            Re: Fixing Garbled Encodings Aidan Kehoe <kehoea@parhasard.net> - 2026-02-24 07:16 +0000
              Re: Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-24 20:24 +0000
                Re: Fixing Garbled Encodings "Henry S. Thompson" <ht@home.hst.name> - 2026-02-24 23:02 +0000
                Re: Fixing Garbled Encodings Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-02-24 23:52 +0000
                Re: Fixing Garbled Encodings "Henry S. Thompson" <ht@home.hst.name> - 2026-02-26 15:35 +0000
                Re: Fixing Garbled Encodings Aidan Kehoe <kehoea@parhasard.net> - 2026-02-26 21:24 +0000
                Re: Fixing Garbled Encodings Aidan Kehoe <kehoea@parhasard.net> - 2026-02-25 06:39 +0000
                Re: Fixing Garbled Encodings Aidan Kehoe <kehoea@parhasard.net> - 2026-02-25 13:55 +0000

csiph-web