Date: Thu, 6 Sep 2012 12:01:06 -0700
From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: Strange behaviour of mutt.exe
Message-ID: <20120906190106.GA12077@phoenix>
Mail-Followup-To: cygwin@cygwin.com
References: <CAGOw3W_r10YBBdhJ0-AQBBzNCSXJvfhNypao4BDRxs5YGSj2yA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAGOw3W_r10YBBdhJ0-AQBBzNCSXJvfhNypao4BDRxs5YGSj2yA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 2012-09-07, Stepan Yakovenko wrote:
> HI!
> 
> To reproduce the problem, launch mutt from command line:
> mutt -f cygwin.mutt.glitch.eml
> 
> open mail and press 'v' to view attachmets. Then press 's' to save
> attachment. Result of saving is different on linux and windows (see
> files attached). Specially, on windows this file has extra B character
> after 'Done:' substring. Looks like a bug. Is there anyone who may
> want to fix it?

The only difference I see between the two attachments att.cygwin and
att.linux is that the former is encoded as UTF-8 while the latter is
encoded as Latin1.  (The latter could have been encoded as something
else, but its encoding is consistent with Latin1.)  That difference
affects the encoding of three non-breaking spaces:

    - between "> >" and " can"
    - after "PS:"
    - after "Done:"

The non-breaking space is 0xa0 in Latin1 and 0xc2a0 in UTF-8.  I
think that 0xc2 is being rendered as a B in whatever you're using to
view that file.  The only problem is that that viewer doesn't know
it's looking at UTF-8.

Regards,
Gary


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple