From: riccardo.murri@gmail.com
Subject: Re: how to find encoding violations in Emacs buffer?
Date: 13 Dec 2006 00:39:57 -0800 [thread overview]
Message-ID: <1165999197.876027.315040@73g2000cwn.googlegroups.com> (raw)
In-Reply-To: <mailman.1814.1165984004.2155.help-gnu-emacs@gnu.org>
On Dec 13, 5:26 am, Eli Zaretskii <e... -at- gnu.org> wrote:
> > From: riccardo.mu... -at- gmail.com
> > Date: 12 Dec 2006 10:18:13 -0800
>
> > 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?
>
> Emacs 22 already shows the problematic characters. Please look closer
> at the text of the buffer where Emacs tells you why it needs your
> decision about the encoding.
Yes, but it may be hard to spot one single problematic character in a
large buffer. In the case at hand, I had one Latin-1 "ù" in a 20k
UTF-8 text, and, since the encoding was thus incorrect and could not
be autodetected, Emacs displayed al non-ASCII characters as \xxx
escape sequences...
Isn't there a way to implement a "goto-next-problematic-char" elisp
function? UTF-8 has a rather simple algorithm to detect encoding
violations, which can point at the precise point where a byte sequence
violates UTF-8 rules, but I wondered if Emacs had a more general
interface: if it knows where in the buffer the encoding violations
are located, one would assume that this information would be available
at elisp level.
Riccardo
next prev parent reply other threads:[~2006-12-13 8:39 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
[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 [this message]
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=1165999197.876027.315040@73g2000cwn.googlegroups.com \
--to=riccardo.murri@gmail.com \
/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).