From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Francesco Potorti` Newsgroups: gmane.emacs.devel Subject: Re: Rmail-mbox branch Date: Mon, 08 Sep 2008 10:36:13 +0200 Message-ID: References: <87zlprvod0.fsf@stupidchicken.com> <4868CF84.1040005@pajato.com> <48A90589.4020804@pajato.com> <48A91146.60200@pajato.com> <48A968A3.8050806@pajato.com> <48BA1DAE.2030005@pajato.com> <874p51xblf.fsf@cyd.mit.edu> <84od39q9mv.fsf@boris.laptop> <84abesum0g.fsf@boris.laptop> <841w03v389.fsf@boris.laptop> <84wshvtgoz.fsf@boris.laptop> <87od363q1i.fsf@uwakimon.sk.tsukuba.ac.jp> <87iqtd4ubu.fsf@uwakimon.sk.tsukuba.ac.jp> <877i9s4pf5.fsf@uwakimon.sk.tsukuba.ac.jp> <87hc8vf97n.fsf@xemacs.org> <878wu3fd4r.fsf@xemacs.org> NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1220863041 24663 80.91.229.12 (8 Sep 2008 08:37:21 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 8 Sep 2008 08:37:21 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@IRO.UMontreal.CA, rms@gnu.org, evilborisnet@netscape.net To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 08 10:38:16 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KccG7-00058M-2N for ged-emacs-devel@m.gmane.org; Mon, 08 Sep 2008 10:38:07 +0200 Original-Received: from localhost ([127.0.0.1]:33901 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KccEz-0002b0-LQ for ged-emacs-devel@m.gmane.org; Mon, 08 Sep 2008 04:36:57 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KccEu-0002aE-2y for emacs-devel@gnu.org; Mon, 08 Sep 2008 04:36:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KccEs-0002ZZ-8l for emacs-devel@gnu.org; Mon, 08 Sep 2008 04:36:51 -0400 Original-Received: from [199.232.76.173] (port=57438 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KccEs-0002ZW-60 for emacs-devel@gnu.org; Mon, 08 Sep 2008 04:36:50 -0400 Original-Received: from mx2.isti.cnr.it ([194.119.192.4]:4455) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KccEm-0006RM-Dz; Mon, 08 Sep 2008 04:36:45 -0400 Original-Received: from conversionlocal.isti.cnr.it by mx.isti.cnr.it (PMDF V6.4-beta #31598) id <01MZBDRTBP9S8Y5HKN@mx.isti.cnr.it>; Mon, 08 Sep 2008 10:36:19 +0200 Original-Received: from tucano.isti.cnr.it (tucano.isti.cnr.it [146.48.81.102]) by mx.isti.cnr.it (PMDF V6.4-beta #31599) with ESMTPSA id <01MZBDRR61ZG90N0IF@mx.isti.cnr.it>; Mon, 08 Sep 2008 10:36:15 +0200 Original-Received: from pot by tucano.isti.cnr.it with local (Exim 4.69) (envelope-from ) id 1KccEH-0006SN-Om; Mon, 08 Sep 2008 10:36:13 +0200 In-reply-to: <878wu3fd4r.fsf@xemacs.org> X-INSM-ip-source: 146.48.81.102 Auth Done X-fingerprint: 4B02 6187 5C03 D6B1 2E31 7666 09DF 2DC9 BE21 6115 X-detected-kernel: by monty-python.gnu.org: OpenVMS 7.2 (Multinet 4.3-4.4 stack) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:103675 Archived-At: >[3] For practical purposes we can assume that message bodies which are >'text/plain; charset=XYZ' for XYZ=iso-8859-1, XYZ=iso-8859-15, and >XYZ=utf-8 will generally "just work", too. But it's easy to imagine >situations where a MIME-conforming MUA might render such incorrectly >without a MIME Content-Type header to guide it, such as a Latin-2- >using locale. One thing that I find useful is searching mbox files using standard Unix text tools. This is not possible for base-64 coded messages. However, I can edit an mbox file, convert its text from base-64 and edit the MIME header appropriately, thus still obtaining an RFC-compliant message that is searchable and that can be displayed without further decoding (it is smaller, too). I do this routinely for the three charsets you mentioned above, but it should work for any charset. I suggest that this conversion be made automatically whenever possible and sensible.