Re: [PATCH v3 0/3] Clean up reply's encoding story

Subject: Re: [PATCH v3 0/3] Clean up reply's encoding story

Date: Sat, 17 Aug 2013 17:21:55 +0200

To: Jani Nikula, Austin Clements, notmuch@notmuchmail.org

Cc: tomi.ollila@iki.fi

From: David Bremner

Jani Nikula <jani@nikula.org> writes:
>
> 'make test' now gives me:
>
>  FAIL   Reply with RFC 2047-encoded headers
> 	--- reply.12.expected	2013-08-17 11:57:31.047782938 +0000
> 	+++ reply.12.output	2013-08-17 11:57:31.047782938 +0000
> 	@@ -1,5 +1,5 @@
> 	 From: Notmuch Test Suite <test_suite@notmuchmail.org>
> 	-Subject: Re: =?iso-8859-1?b?4N/n?=
> 	+Subject: Re: =?iso-8859-1?B?4N/n?=
> 	 To: =?UTF-8?b?4piD?= <snowman@example.com>
> 	 In-Reply-To: <msg-012@notmuch-test-suite>
> 	 References: <msg-012@notmuch-test-suite>
>
> I'm using libgmime 2.6.16-1 from Debian testing.
>

Oh hmm. now that I upgrade to 2.6.16-1 I see the same thing.  It seems
like something changed in gmime. I think the RFC specifies that ?b is
equivalent to ?B as an encoding marker, so maybe we should normalize
before comparing?

d

Thread: