From mboxrd@z Thu Jan  1 00:00:00 1970
Path: main.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@is.elta.co.il>
Newsgroups: gmane.emacs.devel
Subject: Re: Rmail changes for Emacs 22
Date: Wed, 16 Oct 2002 08:09:02 +0200 (IST)
Sender: emacs-devel-admin@gnu.org
Message-ID: <Pine.SUN.3.91.1021016080428.20518C-100000@is>
References: <E181fx7-000067-00@fencepost.gnu.org>
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Trace: main.gmane.org 1034748563 7643 80.91.224.249 (16 Oct 2002 06:09:23 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Wed, 16 Oct 2002 06:09:23 +0000 (UTC)
Cc: emacs-devel@gnu.org, pmr@pajato.com
Return-path: <emacs-devel-admin@gnu.org>
Original-Received: from quimby.gnus.org ([80.91.224.244])
	by main.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 181hMv-0001z7-00
	for <emacs-devel@main.gmane.org>; Wed, 16 Oct 2002 08:09:21 +0200
Original-Received: from monty-python.gnu.org ([199.232.76.173])
	by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian))
	id 181iEF-0007N8-00
	for <emacs-devel@quimby.gnus.org>; Wed, 16 Oct 2002 09:04:27 +0200
Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org)
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 181hMk-0003r7-00; Wed, 16 Oct 2002 02:09:10 -0400
Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10)
	id 181hMW-0003RM-00
	for emacs-devel@gnu.org; Wed, 16 Oct 2002 02:08:56 -0400
Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10)
	id 181hMS-0003FU-00
	for emacs-devel@gnu.org; Wed, 16 Oct 2002 02:08:55 -0400
Original-Received: from is.elta.co.il ([199.203.121.2])
	by monty-python.gnu.org with esmtp (Exim 4.10)
	id 181hMQ-00035h-00; Wed, 16 Oct 2002 02:08:51 -0400
Original-Received: from is (is [199.203.121.2])
	by is.elta.co.il (8.9.3/8.8.8) with SMTP id IAA20912;
	Wed, 16 Oct 2002 08:09:02 +0200 (IST)
X-Sender: eliz@is
Original-To: Richard Stallman <rms@gnu.org>
In-Reply-To: <E181fx7-000067-00@fencepost.gnu.org>
Errors-To: emacs-devel-admin@gnu.org
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Post: <mailto:emacs-devel@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
List-Id: Emacs development discussions. <emacs-devel.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/emacs-devel/>
Xref: main.gmane.org gmane.emacs.devel:8564
X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8564


On Wed, 16 Oct 2002, Richard Stallman wrote:

>     How will the mbox file encoding be treated?
> 
> I don't know, and that is a good question.  I did not work on that
> aspect of Rmail before, and I am not sure what to do about it now.
> We might want to save these files normally in emacs-mule encoding,
> or maybe we would want to decode each message individually when
> displaying it.  pmr@pajato.com is the person doing it.

If this aspect wasn't discussed before, it's probably a good idea to 
discuss that now.

Personally, I think emacs-mule is not a good idea in this case, since 
mbox is not Emacs-private format, so some other software should be able 
to read it.  A good alternative would be to encode each message as what 
the charset= header says (and add/fix such a header if there is none, or 
if the one that's there lies).