[exim-cvs] Fix RFC2047 encoding tests after robustness patch…

Top Page
Delete this message
Reply to this message
Author: Exim Git Commits Mailing List
Date:  
To: exim-cvs
Subject: [exim-cvs] Fix RFC2047 encoding tests after robustness patch.
Gitweb: http://git.exim.org/exim.git/commitdiff/90a3da69b37d9e558012a89afb44ca81d3bda8ac
Commit:     90a3da69b37d9e558012a89afb44ca81d3bda8ac
Parent:     1b587e48d9bb95e6e7d9b3f482a9e4460b6ab130
Author:     Phil Pennock <pdp@???>
AuthorDate: Tue Mar 22 03:37:07 2011 -0400
Committer:  Phil Pennock <pdp@???>
CommitDate: Tue Mar 22 03:37:07 2011 -0400


    Fix RFC2047 encoding tests after robustness patch.


    Output changed by:
      Commit 86ae49a65fce504ebcf9c30ddff213cca71fb872


      Fix wide character breakage in the rfc2047 coding


      Fixes bug 1064
      Patch frome    Andrey N. Oktyabrski
---
 test/stdout/0002 |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)


diff --git a/test/stdout/0002 b/test/stdout/0002
index f343545..c469ce2 100644
--- a/test/stdout/0002
+++ b/test/stdout/0002
@@ -546,8 +546,8 @@
 > abcd      abcd
 > <:abcd:>  =?iso-8859-8?Q?=3C=3Aabcd=3A=3E?=
 > <:ab cd:> =?iso-8859-8?Q?=3C=3Aab_cd=3A=3E?=

-> Long:     =?iso-8859-8?Q?_here_we_go=3A_a_string_that_is_going_to_be_encoded=3A_i?= =?iso-8859-8?Q?t_will_go_over_the_75-char_limit?=
-> Long:     =?iso-8859-8?Q?_here_we_go=3A_a_string_that_is_going_to_be_encoded=3A_i?= =?iso-8859-8?Q?t_will_go_over_the_75-char_limit_by_a_long_way=3B_in_fac?= =?iso-8859-8?Q?t_this_one_will_go_over_the_150_character_limit?=
+> Long:     =?iso-8859-8?Q?_here_we_go=3A_a_string_that_is_going_to_be_encoded=3A_?= =?iso-8859-8?Q?it_will_go_over_the_75-char_limit?=
+> Long:     =?iso-8859-8?Q?_here_we_go=3A_a_string_that_is_going_to_be_encoded=3A_?= =?iso-8859-8?Q?it_will_go_over_the_75-char_limit_by_a_long_way=3B_in?= =?iso-8859-8?Q?_fact_this_one_will_go_over_the_150_character_limit?=

>
> # RFC 2047 decode
>