Re: [PATCH] proc: fixup (c) sign

From: Linus Torvalds
Date: Thu Apr 12 2018 - 16:16:13 EST


On Thu, Apr 12, 2018 at 12:50 PM, Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
>
> I've checked earlier mails, mutt has been "guessing" outgoing encoding
> by default. Let's try again.

I think it still does. This email came with

Content-Type: text/plain; charset=us-ascii

which is what I'd expect if Mutt has a "use the least complex charset
that can fit the message".

If you look at my emails, you should see

Content-Type: text/plain; charset="UTF-8"

even for an email like this, that only has 7-bit ascii.

I'm not a Mutt user, so I don't know what the magic is for "just force
utf-8 when sending".

For alpine, it's

posting-character-set=UTF-8

in the .pinerc file.

For gmail there used to be an "outgoing message encoding" setting, but
it seems to have been removed (and now utf-8 is always on).

Linus