From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Rmail changes for Emacs 22 Date: Wed, 16 Oct 2002 16:19:37 +0900 (JST) Sender: emacs-devel-admin@gnu.org Message-ID: <200210160719.QAA05776@etlken.m17n.org> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1034980402 31463 80.91.224.249 (18 Oct 2002 22:33:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 18 Oct 2002 22:33:22 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org, pmr@pajato.com Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 182fgE-0008B0-00 for ; Sat, 19 Oct 2002 00:33:18 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 182gYq-0000iy-00 for ; Sat, 19 Oct 2002 01:29:44 +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 182ecV-0007hE-00; Fri, 18 Oct 2002 17:25:23 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 182ebr-0007Ud-00 for emacs-devel@gnu.org; Fri, 18 Oct 2002 17:24:43 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 182ebp-0007U7-00 for emacs-devel@gnu.org; Fri, 18 Oct 2002 17:24:42 -0400 Original-Received: from gnudist.gnu.org ([199.232.41.7]) by monty-python.gnu.org with esmtp (Exim 4.10) id 182d64-00076S-00; Fri, 18 Oct 2002 15:47:48 -0400 Original-Received: from tsukuba.m17n.org ([192.47.44.130]) by gnudist.gnu.org with esmtp (Exim 4.10) id 181ibK-0001pW-00; Wed, 16 Oct 2002 03:28:18 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6/3.7W-20010518204228) with ESMTP id g9G7Jck20913; Wed, 16 Oct 2002 16:19:38 +0900 (JST) (envelope-from handa@m17n.org) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.3/3.7W-20010823150639) with ESMTP id g9G7JbR23419; Wed, 16 Oct 2002 16:19:38 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id QAA05776; Wed, 16 Oct 2002 16:19:37 +0900 (JST) Original-To: eliz@is.elta.co.il In-reply-to: (message from Eli Zaretskii on Wed, 16 Oct 2002 08:09:02 +0200 (IST)) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) 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:8567 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8567 In article , Eli Zaretskii writes: >> 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). I agree with that approach. I think we can proceed the modification of rmail in these steps. (1) Divide the current code into BABYL format handler (babyl-backend) and rmail user-interface provider (rmail-frontend). Babyl-backend reads a BABYL file without any code conversion in an unibyte buffer, and provides various functions (e.g. extract message headers, extract a specific message header, extract a message body, get new messages, etc). (2) Make mbox-backend that provides the same facilities as babyl-backend. (3) Make rmail-frontend to use babyl-backend or mbox-backend depending on users mail file. Rmail-frontend displays a message in a different buffer (rmail-view-buffer) than the original mail file buffer. Rmail-frontend utilizes MIME handler to decode message headers and body. This way, we can easiy add more backends, for instance, IMAP, per-message files (like MH or GNUS), etc. --- Ken'ichi HANDA handa@m17n.org