From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: larsi@gnus.org, sebastian_rose@gmx.de, 5050@debbugs.gnu.org
Subject: bug#5050: 23.1; efiff: Displaying bytes instead of characters in messages
Date: Thu, 20 Aug 2020 23:14:36 +0300 [thread overview]
Message-ID: <83pn7laxcj.fsf@gnu.org> (raw)
In-Reply-To: <87a6ypt7sf.fsf@gmx.net> (message from Stephen Berman on Thu, 20 Aug 2020 21:51:44 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Thu, 20 Aug 2020 21:51:44 +0200
> Cc: Sebastian Rose <sebastian_rose@gmx.de>, 5050@debbugs.gnu.org
>
> > This is the problem: ediff-coding-system-for-read is raw-text, which
> > gives us the binary data in the buffer instead of characters.
>
> Indeed, and when I set ediff-coding-system-for-read to utf-8 and carry
> out the OP's recipe, the German text is displayed as it should be with
> umlaut.
Does setting ediff-coding-system-for-read to utf-8 botch comparison of
files that are encoded in something other than UTF-8? I think it
will, so this is not the right solution. Our problem is only with the
messages that end up in the Ediff error buffer.
prev parent reply other threads:[~2020-08-20 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 20:13 bug#5050: 23.1; efiff: Displaying bytes instead of characters in messages Sebastian Rose
2009-11-27 16:01 ` Kevin Rodgers
2020-08-20 18:38 ` Lars Ingebrigtsen
2020-08-20 18:53 ` Stephen Berman
2020-08-20 19:21 ` Eli Zaretskii
2020-08-20 19:35 ` Stephen Berman
2020-08-20 19:42 ` Eli Zaretskii
2020-08-20 19:28 ` Lars Ingebrigtsen
2020-08-20 19:42 ` Lars Ingebrigtsen
2020-08-20 19:50 ` Eli Zaretskii
2020-08-20 20:01 ` Lars Ingebrigtsen
2020-08-20 20:12 ` Eli Zaretskii
2020-08-20 20:18 ` Lars Ingebrigtsen
2020-08-20 20:24 ` Lars Ingebrigtsen
2020-08-20 20:36 ` Stephen Berman
2020-08-21 11:21 ` Lars Ingebrigtsen
2020-08-20 20:17 ` Lars Ingebrigtsen
2020-08-20 19:51 ` Stephen Berman
2020-08-20 20:14 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pn7laxcj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=5050@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sebastian_rose@gmx.de \
--cc=stephen.berman@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.