From: Serge Z <triumhiz@yandex.ru>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] test: Add test for searching of uncommonly encoded messages
Date: Sat, 25 Feb 2012 12:36:00 +0400 [thread overview]
Message-ID: <20120225083600.17873.66388@localhost> (raw)
In-Reply-To: <874nugiq2g.fsf@steelpick.2x.cz>
Hi!
I've struck another problem:
I've got an html/text email with body encoded with cp1251.
Its encoding is mentioned in both Content-type: email header and html <meta>
tag. So when the client tries to display it with external html2text converter,
The message is decoded twice: first by client, second by html2text (I use w3m).
As I understand, notmuch (while indexing this message) decodes it once and
index it in the right way (though including html tags to index). But what if
the message contains no "charset" option in Content-Type email header but
contain <meta> content-type tag with charset noted? Should such message be
considered as being composed wrong or it should be indexed with diving into
html details (content-type)?
next prev parent reply other threads:[~2012-02-26 3:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 17:10 Searching through different charsets Serge Z
2012-02-24 0:31 ` Michal Sojka
2012-02-24 0:33 ` [PATCH] test: Add test for searching of uncommonly encoded messages Michal Sojka
2012-02-24 4:29 ` Serge Z
2012-02-24 7:00 ` Michal Sojka
2012-02-24 7:57 ` Serge Z
2012-02-24 8:38 ` Michal Sojka
2012-02-25 8:36 ` Serge Z [this message]
2012-02-26 9:33 ` Double decoded text/html parts (was: [PATCH] test: Add test for searching of uncommonly encoded messages) Michal Sojka
2012-02-26 10:20 ` Serge Z
2012-02-24 7:36 ` [PATCH 1/2] Convert non-UTF-8 parts to UTF-8 before indexing them Michal Sojka
2012-02-24 7:36 ` [PATCH 2/2] test: Remove 'broken' flag from encoding test Michal Sojka
2012-02-25 4:33 ` [PATCH 1/2] Convert non-UTF-8 parts to UTF-8 before indexing them Austin Clements
2012-02-29 11:55 ` David Bremner
2012-02-29 11:55 ` [PATCH] test: Add test for searching of uncommonly encoded messages David Bremner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120225083600.17873.66388@localhost \
--to=triumhiz@yandex.ru \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).