Re: [PATCH] format-patch: RFC 2047 says multi-octet character may not be split

On Sat, Mar 09, 2013 at 11:07:19AM -0800, Junio C Hamano wrote: > Kirill Smelkov writes: > > P.S. sorry for the delay - I harmed my arm yesterday. > > Ouch. Take care and be well soon. Thanks, and thanks fr accepting the patch. -- To unsubscribe from this list: send the line "unsubscribe git" in

Re: [PATCH] format-patch: RFC 2047 says multi-octet character may not be split

On Sat, Mar 09, 2013 at 07:27:23PM +0400, Kirill Smelkov wrote: > 8< > From: Kirill Smelkov > split Sorry for the confusion... 8< From: Kirill Smelkov Even though an earlier attempt (bafc478..41dd00bad) cleaned up RFC 2047 encoding, pretty.c::add_rfc2047() still decides wh

Re: [PATCH] format-patch: RFC 2047 says multi-octet character may not be split

On Thu, Mar 07, 2013 at 10:05:30AM -0800, Junio C Hamano wrote: > Kirill Smelkov writes: > > >> > @@ -367,16 +376,18 @@ static void add_rfc2047(struct strbuf *sb, const > >> > char *line, int len, > >> > * causes ' ' to be encoded as '=20', avoiding this > >> > problem. > >> >

Re: [PATCH] format-patch: RFC 2047 says multi-octet character may not be split

Junio, On Wed, Mar 06, 2013 at 09:47:53AM -0800, Junio C Hamano wrote: > Kirill Smelkov writes: > > > Intro > > - > > Drop this. We know the beginning part is "intro" already ;-) :) > > Subject: föö bar > > > > encoding > > > > Subject: =?UTF-8?q?=20f=C3=B6=C3=B6?= > >

[PATCH] format-patch: RFC 2047 says multi-octet character may not be split

Intro - In 'Subject:' characters are encoded in Q encoding, as per RFC 2047, e.g. föö becomes =?UTF-8?q?f=C3=B6=C3=B6?= . Long encoded lines must be wrapped to be no longer than 76 bytes. Also RFC 2047, section 5 (3) says: Each 'encoded-word' MUST represent an integral number