1 Return-Path: <sojka@os.inf.tu-dresden.de>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id EFDED431FBC
\r
6 for <notmuch@notmuchmail.org>; Thu, 23 Feb 2012 16:31:38 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id sq6GnxX4aFYZ for <notmuch@notmuchmail.org>;
\r
16 Thu, 23 Feb 2012 16:31:38 -0800 (PST)
\r
17 Received: from max.feld.cvut.cz (max.feld.cvut.cz [147.32.192.36])
\r
18 by olra.theworths.org (Postfix) with ESMTP id 274E1431FAE
\r
19 for <notmuch@notmuchmail.org>; Thu, 23 Feb 2012 16:31:38 -0800 (PST)
\r
20 Received: from localhost (unknown [192.168.200.4])
\r
21 by max.feld.cvut.cz (Postfix) with ESMTP id 11AAD19F330A;
\r
22 Fri, 24 Feb 2012 01:31:37 +0100 (CET)
\r
23 X-Virus-Scanned: IMAP AMAVIS
\r
24 Received: from max.feld.cvut.cz ([192.168.200.1])
\r
25 by localhost (styx.feld.cvut.cz [192.168.200.4]) (amavisd-new,
\r
27 with ESMTP id OyDXVwAxqspK; Fri, 24 Feb 2012 01:31:36 +0100 (CET)
\r
28 Received: from imap.feld.cvut.cz (imap.feld.cvut.cz [147.32.192.34])
\r
29 by max.feld.cvut.cz (Postfix) with ESMTP id 2C8E219F32F4;
\r
30 Fri, 24 Feb 2012 01:31:36 +0100 (CET)
\r
31 Received: from steelpick.2x.cz (cable-86-56-3-85.cust.telecolumbus.net
\r
32 [86.56.3.85]) (Authenticated sender: sojkam1)
\r
33 by imap.feld.cvut.cz (Postfix) with ESMTPSA id 1CF9F660968;
\r
34 Fri, 24 Feb 2012 01:31:36 +0100 (CET)
\r
35 Received: from wsh by steelpick.2x.cz with local (Exim 4.77)
\r
36 (envelope-from <sojka@os.inf.tu-dresden.de>)
\r
37 id 1S0j4R-0005dL-EW; Fri, 24 Feb 2012 01:31:35 +0100
\r
38 From: Michal Sojka <sojkam1@fel.cvut.cz>
\r
39 To: Serge Z <triumhiz@yandex.ru>, notmuch@notmuchmail.org
\r
40 Subject: Re: Searching through different charsets
\r
41 In-Reply-To: <20120222171041.11455.92079@localhost>
\r
42 References: <20120222171041.11455.92079@localhost>
\r
43 User-Agent: Notmuch/0.11.1+210~g5c2fc0a (http://notmuchmail.org) Emacs/23.3.1
\r
44 (x86_64-pc-linux-gnu)
\r
45 Date: Fri, 24 Feb 2012 01:31:35 +0100
\r
46 Message-ID: <877gzd5axk.fsf@steelpick.2x.cz>
\r
48 Content-Type: text/plain; charset=us-ascii
\r
49 X-BeenThere: notmuch@notmuchmail.org
\r
50 X-Mailman-Version: 2.1.13
\r
52 List-Id: "Use and development of the notmuch mail system."
\r
53 <notmuch.notmuchmail.org>
\r
54 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
55 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
56 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
57 List-Post: <mailto:notmuch@notmuchmail.org>
\r
58 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
59 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
60 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
61 X-List-Received-Date: Fri, 24 Feb 2012 00:31:39 -0000
\r
63 On Wed, 22 Feb 2012, Serge Z wrote:
\r
67 > I've got the following problem: fetched emails can be in different encodings.
\r
68 > And searching a term typed in one encoding (system default) does not match the
\r
69 > same term in another encoding.
\r
71 > The solution, as I see, can be in preprocessing each incoming email to
\r
72 > "normalize" it and its encoding so that indexer will handle emails in system
\r
73 > encoding only. Could you please suggest something?
\r
75 I can confirm this issue and sending a patch with test case (marked as
\r
76 broken) for this. I expect the fix to be quite simple because all
\r
77 encoding/docoding stuff is already implemented in gmime which is used by
\r
78 notmuch when indexing.
\r
81 > Another issue (not so much wanted but wanted too) is searching through html
\r
82 > messages without matching html tags.
\r
84 I don't know whether somebody works on this or nor.
\r
86 > This problem looks to be solvable by properly configured run-mailcap. Is there
\r
87 > such solution anywhere?
\r
89 I don't think that run-mailcap has anything to do with notmuch.
\r