all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: mark.lillibridge@hp.com
Cc: emacs-devel@gnu.org
Subject: Re: Rmail and the raw-text coding system
Date: Mon, 17 Jan 2011 14:19:10 -0500	[thread overview]
Message-ID: <jwvy66jqr2y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <qmhhbd88pna.fsf@hp.com> (Mark Lillibridge's message of "Sun, 16 Jan 2011 14:11:53 -0800")

>> >     I assume it did so because the buffer contained "invalid" code
>> > points.
>> That would mean that the BABYL file is corrupted.  Is it?

>     Not as far as I can tell.  Weird characters are displayed for some
> messages, but that is normal with Rmail 22 as it doesn't understand
> MIME.  I believe the use of raw-text does not lose data.

The BABYL file is supposed to use the emacs-mule encoding.  So if it
contains invalid emacs-mule byte sequences, it presumably means
it's corrupted.  Of course, maybe they are valid sequences which
Emacs23/24 rejects by mistake, or maybe there's yet something else
going on.

But AFAIK BABYL files use a single encoding for the whole file, and
since around Emacs-21.x that single encoding is supposed to be
emacs-mule (and I seem to remember that the BABYL file is supposed to
contain an annotation at the very beginning saying it's using
emacs-mule, if so).


        Stefan




  reply	other threads:[~2011-01-17 19:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-14 18:14 Rmail and the raw-text coding system Mark Lillibridge
2011-01-14 21:00 ` Stefan Monnier
2011-01-15  0:06   ` Mark Lillibridge
2011-01-15  2:55     ` Stefan Monnier
2011-01-16 22:11       ` Mark Lillibridge
2011-01-17 19:19         ` Stefan Monnier [this message]
2011-01-17 22:31           ` Mark Lillibridge
2011-01-18  2:05             ` Stefan Monnier
2011-01-19  5:16               ` Mark Lillibridge

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=jwvy66jqr2y.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=mark.lillibridge@hp.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.
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.