[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFywY3tGC-82cJ2utqP4n7AnSvFOiqW7OSk0=MfEwsPS8A@mail.gmail.com>
Date: Wed, 19 Jul 2017 17:53:30 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND v4] MAINTAINERS: fix lots of alphabetic ordering
On Wed, Jul 19, 2017 at 5:35 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> Your mailer is crap, and destroys utf-8 characters. In particular:
>
> -M: Michał Mirosław <mirq-linux@...e.qmqm.pl>
Using pseudo-MIME-encoding, that was actually (before my cut-and-paste
mangled it even more):
Micha=c3=85=c2=82 Miros=c3=85=c2=82aw
> should be
>
> -M: Michał Mirosław <mirq-linux@...e.qmqm.pl>
And the correct utf-8 is
Micha=C5=82 Miros=C5=82aw
and it *looks* like what happened is that something thought the input
was Latin1, and converted the Latin1 to UTF-8.
So the utf-8 character 'ł' (two bytes: =C5=82) was seen as two Latin1
character bytes: =c5 and =82.
And then each of those were converted mindlessly to utf-8, so the 'c5'
character became '=C3=85' and the '82' character became '=c2=82'.
So you have something that believes that a source file was latin1.
May I suggest just making absolutely *everything* on your system use a
utf-8 locale?
Because in this day and age, anything but utf-8 is just woefully
broken crud. "Just say no".
Linus
Powered by blists - more mailing lists