Re: [PATCH 01/10] Add a birdview-on-the-source-code section to the user manual

From: Karl Hasselström <kha@treskal.com>
Date: May 14, 2007, 18:58 UTC
Message-ID: <20070514185852.GA32331@diana.vm.bytemark.co.uk>
In-Reply-To: <20070514183931.GC23090@fieldses.org>

On 2007-05-14 14:39:31 -0400, J. Bruce Fields wrote:

Show 7 quoted lines

> No, I appreciate the complaint, I just don't know what to do about
> it--as far as I can tell, I've chosen utf-8 everywhere I can: my
> commits are in utf-8, and "locale" run from the shell reports
> everything as "en_US.UTF-8". But I suspect the problem is on my end
> somewhere--do I need to do something to make sure mail I send gets a
> header identifying it as utf-8 and not iso-8859-1? I'll investigate
> some more tonight if I get the chance; any advice welcomed.

Your mail headers include this:

  Content-Transfer-Encoding: QUOTED-PRINTABLE
  Content-Type: TEXT/PLAIN; charset=ISO-8859-1

but the mail body has this:

  It includes modifications as suggested by J. Bruce Fields, Karl
  Hasselstr=C3=B6m and Daniel Barkalow.

(That's a two-byte sequence for a single character, which indicates utf8 and rules out latin1.)

I guess the program that generates the e-mail (git-format-patch?) thinks it's getting latin1 input, when it's in fact getting utf8 input. This is the exact same error (or rather, the exact same symptom) that's happened once or twice the last week or so.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle