From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Alexander Pohoyda Newsgroups: gmane.emacs.devel Subject: Re: RMAIL, MIME-related bug Date: 20 Oct 2003 07:21:53 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87wub0cwlq.fsf@oak.pohoyda.family> References: <200310121947.h9CJlhKH006102@oak.pohoyda.family> <874qy4vbg7.fsf@mail.jurta.org> <200310200418.NAA04336@etlken.m17n.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1066627418 21257 80.91.224.253 (20 Oct 2003 05:23:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 20 Oct 2003 05:23:38 +0000 (UTC) Cc: juri@jurta.org, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Oct 20 07:23:35 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 1ABSVy-0002ZM-00 for ; Mon, 20 Oct 2003 07:23:34 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ABSVy-0005eG-00 for ; Mon, 20 Oct 2003 07:23:34 +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 1ABSVU-0006bo-CE for emacs-devel@quimby.gnus.org; Mon, 20 Oct 2003 01:23:04 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ABSVE-0006aQ-Cf for emacs-devel@gnu.org; Mon, 20 Oct 2003 01:22:48 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ABSUi-0006IE-FI for emacs-devel@gnu.org; Mon, 20 Oct 2003 01:22:47 -0400 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.24) id 1ABSUh-0006HQ-Vm for emacs-devel@gnu.org; Mon, 20 Oct 2003 01:22:16 -0400 Original-Received: (qmail 15232 invoked by uid 65534); 20 Oct 2003 05:22:12 -0000 Original-Received: from p508BF3D1.dip.t-dialin.net (EHLO oak.pohoyda.family) (80.139.243.209) by mail.gmx.net (mp009) with SMTP; 20 Oct 2003 07:22:12 +0200 X-Authenticated: #14602519 Original-Received: from oak.pohoyda.family (oak.pohoyda.family [127.0.0.1]) by oak.pohoyda.family (8.12.9/8.12.9) with ESMTP id h9K5LxCN000425; Mon, 20 Oct 2003 07:22:05 +0200 (CEST) (envelope-from alexander.pohoyda@gmx.net) Original-Received: (from apog@localhost) by oak.pohoyda.family (8.12.9/8.12.9/Submit) id h9K5LroS000418; Mon, 20 Oct 2003 07:21:53 +0200 (CEST) (envelope-from alexander.pohoyda@gmx.net) X-Authentication-Warning: oak.pohoyda.family: apog set sender to alexander.pohoyda@gmx.net using -f Original-To: Kenichi Handa In-Reply-To: <200310200418.NAA04336@etlken.m17n.org> Original-Lines: 42 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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:17254 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17254 Kenichi Handa 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. I like these ideas very much and I'll keep them in my mind. Thank you very much! -- Alexander Pohoyda PGP Key fingerprint: 7F C9 CC 5A 75 CD 89 72 15 54 5F 62 20 23 C6 44