tools.linux.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Konstantin Ryabitsev" <konstantin@linuxfoundation.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: tools@linux.kernel.org
Subject: Re: b4: UTF-8 in replies
Date: Thu, 1 Oct 2020 15:26:00 -0400	[thread overview]
Message-ID: <20201001192600.fo2rivqc4nklw4oj@chatter.i7.local> (raw)
In-Reply-To: <20201001184109.GB23339@qmqm.qmqm.pl>

On Thu, Oct 01, 2020 at 08:41:09PM +0200, Michał Mirosław wrote:
> > At least K9 Mail on Android requires MIME headers to properly decode 
> > it.
> > The additional headers are actually required by RFC 5322 to include
> > 8-bit data in the message.
> > 
> > I guess the fix would be to just include Content-Type (and others) with
> > charset="utf8".
> 
> According to RFC2045 those should be enough:
> 
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit

Hrmph, apparently my assumption on what headers will be generated by 
policy=8bit was pretty wrong. I pushed a commit to master and 
stable-0.5.y that should properly set the charset and generate the 
necessary headers.

I intend to cut 0.6.0 tomorrow that will incorporate this fix, among 
several others.

Thanks!
-K

  reply	other threads:[~2020-10-01 19:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201001171405.GA17873@qmqm.qmqm.pl>
2020-10-01 18:05 ` b4: UTF-8 in replies Konstantin Ryabitsev
2020-10-01 18:09   ` [tools] " Mark Brown
2020-10-01 18:36   ` Michał Mirosław
2020-10-01 18:41     ` Michał Mirosław
2020-10-01 19:26       ` Konstantin Ryabitsev [this message]
2020-10-02 21:09         ` [tools] " Mark Brown
2020-10-03 10:13           ` Michał Mirosław
2020-10-03 10:18             ` Michał Mirosław
2020-10-03 14:40               ` Konstantin Ryabitsev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201001192600.fo2rivqc4nklw4oj@chatter.i7.local \
    --to=konstantin@linuxfoundation.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=tools@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).