public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gary Johnson <garyjohn@spocom.com>
To: cygwin@cygwin.com
Subject: Re: Strange behaviour of mutt.exe
Date: Thu, 06 Sep 2012 19:13:00 -0000	[thread overview]
Message-ID: <20120906190106.GA12077@phoenix> (raw)
In-Reply-To: <CAGOw3W_r10YBBdhJ0-AQBBzNCSXJvfhNypao4BDRxs5YGSj2yA@mail.gmail.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

      reply	other threads:[~2012-09-06 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 19:04 Stepan Yakovenko
2012-09-06 19:13 ` Gary Johnson [this message]

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=20120906190106.GA12077@phoenix \
    --to=garyjohn@spocom.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).