unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: how to find encoding violations in Emacs buffer?
Date: Wed, 13 Dec 2006 11:45:21 +0100	[thread overview]
Message-ID: <A26AFD4B-C1EC-4908-BDE9-D4B73D743E97@Web.DE> (raw)
In-Reply-To: <1165999197.876027.315040@73g2000cwn.googlegroups.com>


Am 13.12.2006 um 09:39 schrieb riccardo.murri@gmail.com:

> 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,

This character is an UTF-8 entity:

	[ù]  00F9  LATIN SMALL LETTER U WITH GRAVE

It cannot be the cause. In UTF-8 it's encoded as C3 B9. Kermit and  
Unicode Emacs 23 have a file UnicodeData.txt that describes a lot of  
Unicode characters. A bit more complete is Kermit's utf8.txt from  
which the above excerpt comes.

>
> 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.

There is something like this already implemented in PostScript  
printing: when the buffer contains characters outside a specific ISO  
Latin encoding up to a dozen of them is presented in a warning buffer.

--
Greetings

   Pete
               <\
                 \__     O                       __O
                 | O\   _\\/\-%                _`\<,
                 '()-'-(_)--(_)               (_)/(_)

  reply	other threads:[~2006-12-13 10:45 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
2006-12-13 10:45     ` Peter Dyballa [this message]
     [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=A26AFD4B-C1EC-4908-BDE9-D4B73D743E97@Web.DE \
    --to=peter_dyballa@web.de \
    --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).