From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: bug-gnu-emacs@gnu.org,
Elmar Zander <ezander@valkyrie.sc.cs.tu-bs.de>,
4712@emacsbugs.donarmstrong.com
Subject: bug#4712: File encoding
Date: Wed, 14 Oct 2009 09:27:33 -0400 [thread overview]
Message-ID: <jwvvdii6r9l.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <m3r5t64a3x.fsf@hase.home> (Andreas Schwab's message of "Wed, 14 Oct 2009 11:07:30 +0200")
>> my source file begins with the following lines
>>
>> #!/usr/bin/perl
>> # -*- coding: iso-8859-1 -*-
>> #
>>
>> I definitely need the latin-1 encoding here because the script is supposed
>> to do some non-standard translations from latin-1 to html entities. However,
>> whenever I try to save the file I get the message:
>>
>> Selected encoding mule-utf-8-unix disagrees with iso-8859-1-unix specified by file contents.
>> Really save (else edit coding cookies and try again)? (yes or no)
> That means that the buffer contains characters that cannot be encoded in
> iso-8859-1-unix.
Indeed, but the error message we output is completely unhelpful.
Rather than select utf-8 and then complain that the tag doesn't match,
we should say upfront, that the selected latin-1 can't encode all the
chars in the buffer (and that message can come with the usual thingy
that shows the offending chars and their location).
Stefan
next prev parent reply other threads:[~2009-10-14 13:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 9:12 bug#4712: File encoding Elmar Zander
2009-10-14 9:07 ` Andreas Schwab
2009-10-14 13:27 ` Stefan Monnier [this message]
2009-10-14 14:04 ` Eli Zaretskii
2009-10-14 14:33 ` Andreas Schwab
2009-10-14 18:11 ` Eli Zaretskii
2009-10-14 15:19 ` Stefan Monnier
2009-10-14 18:15 ` Eli Zaretskii
2009-10-15 3:16 ` Stefan Monnier
2009-10-15 7:20 ` Eli Zaretskii
2009-10-15 9:38 ` Andreas Schwab
2009-10-17 4:01 ` Stefan Monnier
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=jwvvdii6r9l.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4712@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=ezander@valkyrie.sc.cs.tu-bs.de \
--cc=schwab@linux-m68k.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 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.