Re: Rmail-mbox branch

[Eli Zaretskii]

> From: Stefan Monnier <address@hidden>
> Cc: Evil Boris <address@hidden>,  address@hidden
> Date: Mon, 01 Sep 2008 15:57:50 -0400
> 
> >> I guess in absense of such support (and hoping etach or equivalent will
> >> magically support mbox format :-), my main concern would be handling of
> >> different character sets (Unicode, ISO-8859-x, KOI8-R, are most popular)
> >> in plain text msgs, so that I can see the text without jumping through
> >> hoops.
> > I don't see why the mbox branch would support this any worse than the
> > trunk.  The decoding stuff is pretty much stable and well understood,
> > after so many releases.
> 
> IIIUC the differnece is that BABYL is encoded using emacs-mule, whereas
> mbox needs to stick to the standard rfc2822+MIME format.  So BABYL can
> be decoded in place once and forall, whereas mbox needs to be decoded
> upon display, more or less.

Yes, but that's the same decoding we do today, and the fact mbox
should do it more than once doesn't make it less correct.