From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Eli Zaretskii" Newsgroups: gmane.emacs.devel Subject: Re: Rmail changes for Emacs 22 Date: Tue, 22 Oct 2002 21:40:45 +0300 Sender: emacs-devel-admin@gnu.org Message-ID: <9743-Tue22Oct2002214045+0200-eliz@is.elta.co.il> References: <84lm4rvvat.fsf@crybaby.cs.uni-dortmund.de> Reply-To: Eli Zaretskii NNTP-Posting-Host: main.gmane.org X-Trace: main.gmane.org 1035315630 18990 80.91.224.249 (22 Oct 2002 19:40:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 22 Oct 2002 19:40:30 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1844t5-0004vc-00 for ; Tue, 22 Oct 2002 21:40:23 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 1844uR-0000lz-00 for ; Tue, 22 Oct 2002 21:41:47 +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 1844sD-0003am-00; Tue, 22 Oct 2002 15:39:29 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 1844rj-00039D-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 15:38:59 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 1844rh-00038x-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 15:38:58 -0400 Original-Received: from freya.inter.net.il ([192.114.186.14]) by monty-python.gnu.org with esmtp (Exim 4.10) id 1844rh-00034h-00 for emacs-devel@gnu.org; Tue, 22 Oct 2002 15:38:57 -0400 Original-Received: from zaretsky ([80.230.194.148]) by freya.inter.net.il (Mirapoint Messaging Server MOS 3.2.0-GA) with ESMTP id BWF58305; Tue, 22 Oct 2002 21:38:46 +0200 (IST) Original-To: Kai.Grossjohann@CS.Uni-Dortmund.DE X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9 In-reply-to: <84lm4rvvat.fsf@crybaby.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:8666 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8666 > From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjohann?=) > Date: Tue, 22 Oct 2002 08:31:38 +0200 > > Eli Zaretskii writes: > > > 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). > > Maybe "encode" is a bit misleading in this case, as the bytes in the > message are not changed (modulo adding/fixing the Content-Type > header). > > It's more the case that the message that's displayed is _de_coded for > viewing, right? Currently, RMAIL decodes the messages in-place, i.e. the encoded text as received from the MTA is replaced in the RMAIL buffer with the decoded text. If this modus operandi is retained, you must encode the text when you save the RMAIL buffer to a file. (I've heard that there was an intent to decode the messages into another buffer, but I don't know whether this is being worked on.)