From: Jani Nikula <jani@nikula.org>
To: Albin Stjerna <albin.stjerna@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Bug: problem decoding some non-ascii characters in subjects
In-Reply-To: <87pq09eu41.fsf@hecate.student.uu.se>
References: <87txpnds0k.fsf@hecate.student.uu.se> <8738x7kq44.fsf@nikula.org>
	<87pq09eu41.fsf@hecate.student.uu.se>
User-Agent: Notmuch/0.14+255~gff3cc55 (http://notmuchmail.org) Emacs/24.2.1
	(x86_64-pc-linux-gnu)
Date: Sat, 09 Feb 2013 12:06:58 +0200
Message-ID: <87mwvd6bst.fsf@nikula.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list

On Sat, 09 Feb 2013, Albin Stjerna <albin.stjerna@gmail.com> wrote:
> 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

Is that entirely on one line in the original message file? If not, where
exactly is it split?

Either way, at a glance, it seems like the encoding is malformed. I
think the encoded-word ("=3D?" charset "?" encoding "?" encoded-text "?=3D")
should be separated by space to make it an atom. [RFC 2047, RFC 2822].

If you manually move the leading 'f' after the "?Q?" bit, it works as
expected. It looks like the bug is in the sender's user agent.


BR,
Jani.