Re: [PATCH] Fix Q-encoded multi-octet-char split in email.

From: Erik Faye-Lund <kusmabite@gmail.com>
Date: Jul 3, 2012, 09:52 UTC
Message-ID: <CABPQNSYbdjzrHyjsXu23ARFBEiZ_a6S+iEn0Pwy-1HaKTTAheQ@mail.gmail.com>
In-Reply-To: <1341279697-4596-1-git-send-email-gkatsu.ne@gmail.com>

On Tue, Jul 3, 2012 at 3:41 AM, katsu <gkatsu.ne@gmail.com> wrote:

Show 14 quoted lines

> Issue: Email subject written in multi-octet language like japanese cannot
> be displayed in correct at destinations's email client, because the
> Q-encoded subject which is longer than 78 octets is split by a octet not by
> a character at line breaks.
> e.g.)
>    "=?utf-8?q? [PATCH] ... =E8=83=86=E8=81=A9?="
>                     |
>                     V
>    "=?utf-8?q? [PATCH] ... =E8=83=86=E8?="
>    "=?utf-8?q?=81=A9=?"
>
> Changes: Add a judge if a character is an part of utf-8 muti-octet, and
> split the characters by a character not by a octet at line breaks in
> function add_rfc2407() in pretty.c.

You mean add_rfc2047(), right?

Anyway, I'm not an expert here, but can't a "soft" newline (as specified in rfc 2045) be used in message headers? If it could, then we wouldn't need to grok the underlying encoding when wrapping, which strikes me as slightly better...