From: Albin Stjerna <albin.stjerna@gmail.com>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Subject: Re: Bug: problem decoding some non-ascii characters in subjects
In-Reply-To: <8738x7kq44.fsf@nikula.org>
References: <87txpnds0k.fsf@hecate.student.uu.se> <8738x7kq44.fsf@nikula.org>
User-Agent: Notmuch/0.14+243~g18d79d1 (http://notmuchmail.org) Emacs/24.3.50.1
	(x86_64-pc-linux-gnu)
Date: Sat, 09 Feb 2013 10:04:14 +0100
Message-ID: <87pq09eu41.fsf@hecate.student.uu.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list

Jani Nikula wrote:

> On Fri, 08 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:
> > I've been noticing that notmuch has some problems decoding certain
> > strangely-encoded non-ascii characters in certain emails. For example,
> > today I got this: [BIBLIST] Digitaliseringensprojektens skadliga
> > f=3D?ISO-8859-1?Q?=3DF6rk=3DE4rlek_f=3DF6r_?=3D PDF-formatet (should be
> > rendered: =C2=BBDigitaliseringsprojektens skadliga f=C3=B6rk=C3=A4rlek =
f=C3=B6r
> > PDF-formatet=C2=AB).
> >
> > Apparently, some metadata is passed on to help the MUA decode the
> > string, but notmuch doesn't seem to handle it. Entire emails can of
> > course be supplied as needed.

> Please copy paste the Subject: header directly from the message file.

The exact Subject: header (from the file, not notmuch) is:
Subject: [BIBLIST] Digitaliseringensprojektens skadliga f=3D?ISO-8859-1?Q?=
=3DF6rk=3DE4rlek_f=3DF6r_?=3D PDF-formatet

Other potentially interesting headers are:
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106
            Thunderbird/17.0.2
MIME-Version: 1.0
Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed

(formatted as they appeared in the mail file)