From: Tomi Ollila <tomi.ollila@iki.fi>
To: Albin Stjerna <albin.stjerna@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Problem with invalid characters when using notmuch-reply
In-Reply-To: <87r4tvmoeq.fsf@hecate.student.uu.se>
References: <87r4tvmoeq.fsf@hecate.student.uu.se>
User-Agent: Notmuch/0.13.2+7~g08be9ce (http://notmuchmail.org) Emacs/23.1.1
	(x86_64-redhat-linux-gnu)
Date: Mon, 04 Jun 2012 13:09:28 +0300
Message-ID: <m2haurl76v.fsf@guru.guru-group.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: list

On Mon, Jun 04 2012, Albin Stjerna <albin.stjerna@gmail.com> wrote:

> Hi!
>
> I have a very confusing problem. When replying to a message containing
> special characters (read: non-ascii), they show up as mysteriously
> escaped characters, such as \345 (where the letter =C3=A4 should be). When
> sending these replies, I get an error about my message containing
> non-printable characters. When these messages arrive, the special
> characters (even those I entered, that looked fine in the mail compose
> buffer) are garbled.
>
> Everything works fine when composing a new message. The problem only
> appears when replying. The problem appeared quite recently, apparently
> out of nowhere. No emacs upgrade, no notmuch upgrade (as far as I can
> recall).
>
> The problem is appears in both Emacs 23 and 24, and restart (neither of E=
macs nor of my computer) doesn't help.
>
> Also:
> albin@hecate ~ % notmuch --version
> notmuch 0.13

Notmuch 0.13.1 fixed this problem -- excerpt from NEWS file:

Notmuch 0.13.1 (2012-05-29)
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D

Bug-fix release
---------------

Fix inserting of UTF-8 characters from *text/plain* parts in reply

  While notmuch gained ability to insert content from other than
  *text/plain*
  parts of email whenever *text/plain* parts are not available (notably
  HTML-only emails), replying to mails that do have *text/plain* the
  non-ASCII characters were incorrectly decoded. This is now fixed.


>
> albin@hecate ~ % locale
> LANG=3Den_US.utf8
> LANGUAGE=3D
> LC_CTYPE=3D"en_US.utf8"
> LC_NUMERIC=3D"en_US.utf8"
> LC_TIME=3D"en_US.utf8"
> LC_COLLATE=3D"en_US.utf8"
> LC_MONETARY=3D"en_US.utf8"
> LC_MESSAGES=3D"en_US.utf8"
> LC_PAPER=3D"en_US.utf8"
> LC_NAME=3D"en_US.utf8"
> LC_ADDRESS=3D"en_US.utf8"
> LC_TELEPHONE=3D"en_US.utf8"
> LC_MEASUREMENT=3D"en_US.utf8"
> LC_IDENTIFICATION=3D"en_US.utf8"
> LC_ALL=3D
>
> notmuch reply (on the command line) seems to work just fine.
>
> Any pointers you can give me would be greatly appreciated!

Thank you for the good information you provided in your report!

> Thanks in advance,
>   Albin

Tomi