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, MIME-related bug Date: Mon, 20 Oct 2003 13:18:56 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200310200418.NAA04336@etlken.m17n.org> References: <200310121947.h9CJlhKH006102@oak.pohoyda.family> <874qy4vbg7.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1066623678 15771 80.91.224.253 (20 Oct 2003 04:21:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 20 Oct 2003 04:21:18 +0000 (UTC) Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Oct 20 06:21:15 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ABRXf-0000fw-00 for ; Mon, 20 Oct 2003 06:21:15 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ABRXf-0005D8-00 for ; Mon, 20 Oct 2003 06:21:15 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ABRWK-0000He-B3 for emacs-devel@quimby.gnus.org; Mon, 20 Oct 2003 00:19:52 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ABRW3-0000HK-Cc for emacs-devel@gnu.org; Mon, 20 Oct 2003 00:19:35 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ABRVX-0000DZ-Jl for emacs-devel@gnu.org; Mon, 20 Oct 2003 00:19:34 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ABRVW-0000DO-V7 for emacs-devel@gnu.org; Mon, 20 Oct 2003 00:19:03 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6p2/3.7W-20010518204228) with ESMTP id h9K4Iuh08151; Mon, 20 Oct 2003 13:18:56 +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.6/3.7W-20010823150639) with ESMTP id h9K4Ius06455; Mon, 20 Oct 2003 13:18:56 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id NAA04336; Mon, 20 Oct 2003 13:18:56 +0900 (JST) Original-To: juri@jurta.org In-reply-to: <874qy4vbg7.fsf@mail.jurta.org> (message from Juri Linkov on 19 Oct 2003 23:59:22 +0300) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17252 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17252 Juri Linkov writes: > I see one solution to these problems - to export entire mbox to the > file system, i.e. to save MIME parts to separate files, decode > base64/quoted-printable regions, convert the charset from Content-Type > line to Emacs encoding, add corresponding -*- coding: -*- line, and > save fully decoded message to a separate file. > Note that this don't contradict the decision to store messages in mbox > in their undecoded form. The proposed solution duplicates the content > of messages in the decoded form. Hard disks now so cheap that having > two copies of the same message is not a problem. The decoded messages > could also be used as a cache to make displaying messages faster, > whereas undecoded messages will be available to resend forwards, where > no original information should be lost. There should be some way to > correlate between them, i.e. to find corresponding decoded message > from undecoded one, and vice versa. This method is very similar to what I proposed in my previous mail. Kenichi Handa writes: > (1) Read RMAIL file without decoding into some hidden source > buffer (unibyte). It may be ok to process only > Content-Transfer-Encoding. > (2) Prepare a view buffer. > (3) Insert the current message in the view buffer after decoding it. > (4) A background process (run by idle timer?) decodes not > yet decoded message into the view buffer (like > jit-lock-stealth-fontify). Mine doesn't save the view buffer in a file, yours does. --- Ken'ichi HANDA handa@m17n.org