Re: mutt reply enconding problem
- To: mutt-users@xxxxxxxx
- Subject: Re: mutt reply enconding problem
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Sun, 25 Jan 2009 17:29:07 -0600
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=EDBjgSnm2eQ1NFyjGMFHWJxNZ5o=; b=Vg9H wkxlYoRWEKVuRUZh7OM4LikR3WRPaiq0An2B6lZEzKpXmEwFUFN12MZgZuYNxnzI 1xB73PiLRuC0T3gVBhKBleyQMZiYrS4+JLnLZYy4uyUcNxWkh0MphYpZYoicQ7xY smMVhthU/mmx0ePQ4w69vIjhLxdWRT5uDtkISN8=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=LYY89OzDO7lBkq34y1opfyHLkSaGwZ0Vrn08ImhaXPZtFgn2cC+Jqq6GgcJYPBO8fdRHMm1A0x0L1BYm4W43WX02buQYWYgmhZAhcSvnvcEz50k4yooVfmfwLNniwL1Nc5pZPvAHbZEA+PA2lXzcArlBAoFzGJs5iBFHpQ5A9s8=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20090125230723.GA5014@xxxxxxxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20090124155731.GA14197@xxxxxxxxxxxxxxxxxx> <20090125112040.GB1791@xxxxxxxxxxxxxxxxxx> <20090125212802.GA1147@xxxxxxxxxxxxx> <20090125230723.GA5014@xxxxxxxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.19 (2009-01-11)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday, January 26 at 01:07 AM, quoth Dimitris Mandalidis:
> On Sun, Jan 25, 2009 at 03:28:02PM -0600, Kyle Wheeler wrote:
>
>> Now, one of two things must be happening here: either you're receiving
>> correctly encoded messages, mutt is decoding them, and then (for
>> whatever reason, maybe a bug) sending the decoded version to your text
>> editor OR you're receiving badly-encoded messages that do not use RFC
>> 2047 encoding, and mutt is doing its best to display them, but has
>> difficulty formatting them for your text editor due to their
>> brokenness.
>
> Indeed, the iso-8859-7 characters in the subject line were shown as
> escaped octal values.
AH! Perfect - so, mutt didn't know how to handle them at all! Largely
because they're not encoded correctly. They're like sugar in the gas
tank: not what the engine was expecting.
Now, what mutt *should* do, I think, is mask those unprintable
non-recognizable characters when it hands them to the editor, so that
they don't confuse the editor (and to help avoid sending incorrect
headers to other people)... you should probably submit a bug report
(http://dev.mutt.org) so that this gets fixed.
~Kyle
- --
The best way to know God is to love many things.
-- Vincent Van Gogh
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkl89cMACgkQBkIOoMqOI17hqwCeOai1iiJaAak41nEYDYpS9CDq
iRUAnRB1nXaEkh++M+4JquG1q5BLtDof
=ow9r
-----END PGP SIGNATURE-----