diff options
author | Austin Clements <amdragon@MIT.EDU> | 2013-08-19 10:40:03 -0400 |
---|---|---|
committer | David Bremner <bremner@debian.org> | 2013-08-20 09:14:25 +0200 |
commit | e41cd1c518d7c5af565d4bed284bbd8a66366da1 (patch) | |
tree | 0fa30eed16e70aea105fcc713ac2c6ff93648c47 | |
parent | dc51bf0ad4ce84414e79d2f30752502f7c0d46c0 (diff) |
test: Canonicalize RFC 2047 encoding and charset
RFC 2047 states that the encoding and charset in an encoded word are
case-insensitive, so force them to lower case in the reply test. This
fixes an issue caused by GMime versions (somewhere between 2.6.10 and
2.6.16), which changed the capitalization of the encoding.
-rwxr-xr-x | test/reply | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -201,12 +201,14 @@ add_message '[subject]="=?iso-8859-1?q?=e0=df=e7?="' \ '[date]="Tue, 05 Jan 2010 15:43:56 -0000"' \ '[body]="Encoding"' -output=$(notmuch reply id:${gen_msg_id}) -# Note that GMime changes from Q- to B-encoding +# GMime happens to change from Q- to B-encoding. We canonicalize the +# case of the encoding and charset because different versions of GMime +# capitalize the encoding differently. +output=$(notmuch reply id:${gen_msg_id} | perl -pe 's/=\?[^?]+\?[bB]\?/lc($&)/ge') test_expect_equal "$output" "\ From: Notmuch Test Suite <test_suite@notmuchmail.org> Subject: Re: =?iso-8859-1?b?4N/n?= -To: =?UTF-8?b?4piD?= <snowman@example.com> +To: =?utf-8?b?4piD?= <snowman@example.com> In-Reply-To: <${gen_msg_id}> References: <${gen_msg_id}> |