From: "Riccardo Murri" <riccardo.murri@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: how to find encoding violations in Emacs buffer?
Date: Tue, 12 Dec 2006 21:56:32 +0100 [thread overview]
Message-ID: <1c34ba170612121256w79f67512u75db458691ebcc3f@mail.gmail.com> (raw)
In-Reply-To: <457F1399.3040008@student.lu.se>
On 12/12/06, Lennart Borgman <lennart.borgman.073@student.lu.se> wrote:
> riccardo.murri@gmail.com wrote:
> > Hello,
> >
> > from time to time, a buffer gets some spurious character in and Emacs
> > refuses to save it in the correct encoding. So I am presented with the
> > choice of other different encodings.
> >
> > However, in most of the cases, I know that the file *should* be UTF-8
> > encoded. So I would rather like to find out where the offending
> > character is and correct it, instead of choosing a different encoding.
> >
> > Is there any function/package/elisp hack to find/highlight characters
> > in a buffer that Emacs could not encode as UTF-8?
> >
>
> I think someone said there was, but I have never seen it though I have
> had these problem quite often. Can't remember the details now.
>
> Which platform are you on? I am using MS Windows (2000 or XP).
>
Debian (etch) GNU/Linux, running emacs-snapshot-gtk, 22.0.90
Does the platform matter in this case? I would have thought the elisp
interface
hides those details...
Riccardo
next prev parent reply other threads:[~2006-12-12 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 18:18 how to find encoding violations in Emacs buffer? riccardo.murri
2006-12-12 20:39 ` Lennart Borgman
2006-12-12 20:56 ` Riccardo Murri [this message]
[not found] ` <mailman.1801.1165956001.2155.help-gnu-emacs@gnu.org>
2006-12-12 23:45 ` B. T. Raven
2006-12-13 4:26 ` Eli Zaretskii
[not found] ` <mailman.1814.1165984004.2155.help-gnu-emacs@gnu.org>
2006-12-13 8:39 ` riccardo.murri
2006-12-13 10:45 ` Peter Dyballa
[not found] ` <mailman.1823.1166006732.2155.help-gnu-emacs@gnu.org>
2006-12-13 12:34 ` riccardo.murri
2006-12-13 12:55 ` Peter Dyballa
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=1c34ba170612121256w79f67512u75db458691ebcc3f@mail.gmail.com \
--to=riccardo.murri@gmail.com \
--cc=help-gnu-emacs@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.
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).