unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: emacs-devel@gnu.org
Subject: ediff and coding systems
Date: Sat, 20 Oct 2007 08:21:10 -0700	[thread overview]
Message-ID: <200710201521.l9KFLCWK004756@oogie-boogie.ics.uci.edu> (raw)


lisp/term/mac-win.el from CVS trunk uses:  -*-coding: iso-2022-7bit;-*-
and the same file on the emacs-unicode-2 uses: -*-coding: utf-8 

When doing M-x ediff for the above 2 files a *Warning* buffer pops up
for each hunk:

These default coding systems were tried to encode text
in the buffer ` *ediff-tmp*':
  iso-latin-1
However, each of them encountered characters it couldn't encode:
  iso-latin-1 cannot encode these: ? ? ? ? ? ? ? ? ? ? ...

Click on a character (or switch to this window by `C-x o'
and select the characters by RET) to jump to the place it appears,
where `C-u C-x =' will give information about it.

Select one of the safe coding systems listed below,
or cancel the writing with C-g and edit the buffer
   to remove or modify the problematic characters,
or specify any other coding system (and risk losing
   the problematic characters).

  utf-8 utf-16 utf-16 utf-16 utf-16be utf-16le iso-2022-7bit

with the question "Select coding system (default mule-utf-8):"

Would it be possible for ediff to avoid this?

             reply	other threads:[~2007-10-20 15:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-20 15:21 Dan Nicolaescu [this message]
2007-10-20 18:09 ` ediff and coding systems Eli Zaretskii
2007-10-21  5:43   ` Michael Kifer
2007-10-21  6:12     ` Dan Nicolaescu
2007-10-21  6:52       ` Michael Kifer
2007-10-21  7:17         ` Dan Nicolaescu
2007-10-21 18:46           ` Michael Kifer
2007-10-21 19:22             ` Dan Nicolaescu
2007-10-21 19:37               ` Leo
2007-10-21 21:35               ` Michael Kifer
2007-10-22  2:08                 ` Dan Nicolaescu
2007-10-22  3:50                   ` Michael Kifer
2007-10-27 21:03                     ` Dan Nicolaescu
2007-10-28 21:01                       ` Michael Kifer
2007-10-22  3:42               ` Kenichi Handa
2007-10-22  4:20                 ` Eli Zaretskii
2007-10-22  5:05                   ` Kenichi Handa
2007-10-22 15:32                   ` Stefan Monnier
2007-10-22 21:11                     ` Eli Zaretskii
2007-10-22  4:29                 ` Michael Kifer
2007-10-22 15:34                   ` Stefan Monnier
2007-10-22 16:18                     ` Michael Kifer
2007-10-21  2:12 ` Stefan Monnier
2007-10-21  2:43   ` Dan Nicolaescu

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200710201521.l9KFLCWK004756@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).