Your message dated Tue, 8 Sep 2009 05:07:46 +0000
with message-id <[email protected]>
and subject line Re: Bug#541422: mutt: wrong charset when editing message with
headers
has caused the Debian Bug report #541422,
regarding mutt: wrong charset when editing message with headers
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
541422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541422
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 1.5.20-2
When I compose a message to myself in vim, mutt nicely detects from
the locale that it is UTF-8 and transcodes to ascii or iso-8859-1 as
appropriate. (To reproduce: run mutt, m, jrn, Test, a étale <esc> ZZ,
q, y. $HOME/postponed is correctly transcoded to latin1.)
But when I edit a message including headers, mutt skips the
transcoding step. (To reproduce, with the postponed message from
before: run mutt, m, y, ZZ, E, :%s/Test/Testing/ <ret> ZZ, q, y.
$HOME/postponed is UTF-8, but the message header says it should be
iso-8559-1.)
Please let me know if there is any more I can do to help test this.
Thanks,
Jonathan
$ test -e $HOME/.muttrc || echo no muttrc present
no muttrc present
$ echo $LANG
en_US.UTF-8
$ echo ${LC_ALL-unset}
unset
$ dpkg -l vim mutt | tail -2
ii mutt 1.5.20-2 text-based mailreader supporting
MIME, GPG, PG
ii vim 2:7.2.245-2 Vi IMproved - enhanced vi editor
--- End Message ---
--- Begin Message ---
On Sun, Sep 06, 2009 at 09:18:53PM -0500, Jonathan Nieder wrote:
> > tag 541422 +confirmed upstream
>
> Unfortunately, I am no longer able to reproduce it myself :(. Were you able
> to?
Sorry I haven't checked :|
> I fear I must have confused myself somehow, since after screwing up
> the encoding in a few messages I sent with this version of mutt, I do
> not see what in mutt???s or my own behavior could have been fixed.
Don't worry, I will close this bug now, if you have any other problem don't
hesitate to open another bug :-)
Cheers
Antonio
--- End Message ---
