Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-10 Thread Albin Stjerna
Jani Nikula wrote: > It seems to be list mail. It would not surprise me that some ill-advised > mailing list manager would decode and re-encode the subject. One could > try sending the same message directly and through the list, and see if > there's a difference. Possibly, though I don't have the

Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-10 Thread Jani Nikula
On Sun, 10 Feb 2013, Albin Stjerna wrote: > Hm. So I should report this to Thunderbird? I tried searching through > their bug reports but didn't find anything. I tried that too; there were other RFC 2047 related header bugs but could not find this one. And the other bugs were old and fixed. Judgi

Bug: problem decoding some non-ascii characters in subjects

2013-02-10 Thread Jani Nikula
On Sun, 10 Feb 2013, Albin Stjerna wrote: > Hm. So I should report this to Thunderbird? I tried searching through > their bug reports but didn't find anything. I tried that too; there were other RFC 2047 related header bugs but could not find this one. And the other bugs were old and fixed. Judgi

Bug: problem decoding some non-ascii characters in subjects

2013-02-10 Thread Albin Stjerna
Jani Nikula wrote: > It seems to be list mail. It would not surprise me that some ill-advised > mailing list manager would decode and re-encode the subject. One could > try sending the same message directly and through the list, and see if > there's a difference. Possibly, though I don't have the

Bug: problem decoding some non-ascii characters in subjects

2013-02-10 Thread Albin Stjerna
Jani Nikula wrote: > Is that entirely on one line in the original message file? If not, where > exactly is it split? It's in one line. > Either way, at a glance, it seems like the encoding is malformed. I > think the encoded-word ("=?" charset "?" encoding "?" encoded-text "?=") > should be sepa

Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-10 Thread Albin Stjerna
Jani Nikula wrote: > Is that entirely on one line in the original message file? If not, where > exactly is it split? It's in one line. > Either way, at a glance, it seems like the encoding is malformed. I > think the encoded-word ("=?" charset "?" encoding "?" encoded-text "?=") > should be sepa

Bug: problem decoding some non-ascii characters in subjects

2013-02-09 Thread Jani Nikula
On Sat, 09 Feb 2013, Albin Stjerna wrote: > Jani Nikula wrote: > >> On Fri, 08 Feb 2013, Albin Stjerna 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] Digita

Bug: problem decoding some non-ascii characters in subjects

2013-02-09 Thread Albin Stjerna
Jani Nikula wrote: > On Fri, 08 Feb 2013, Albin Stjerna 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=?ISO-8859-1?Q

Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-09 Thread Jani Nikula
On Sat, 09 Feb 2013, Albin Stjerna wrote: > Jani Nikula wrote: > >> On Fri, 08 Feb 2013, Albin Stjerna 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] Digita

Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-09 Thread Albin Stjerna
Jani Nikula wrote: > On Fri, 08 Feb 2013, Albin Stjerna 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=?ISO-8859-1?Q

Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Jani Nikula
On Fri, 08 Feb 2013, Albin Stjerna 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=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-for

Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Albin Stjerna
Hi, 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=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-formatet (should be rendered: ?Digitalisering

Re: Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Jani Nikula
On Fri, 08 Feb 2013, Albin Stjerna 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=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-for

Bug: problem decoding some non-ascii characters in subjects

2013-02-08 Thread Albin Stjerna
Hi, 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=?ISO-8859-1?Q?=F6rk=E4rlek_f=F6r_?= PDF-formatet (should be rendered: »Digitalisering