<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #2990: mutt-1.5.16: utf-8 support broken somewhere



#2990: mutt-1.5.16: utf-8 support broken somewhere between 1.5.13 and 1.5.16

Comment (by Rocco Rutte):

 {{{
 Hi,

 * Mutt wrote:

 >>  Can you please give the following information: the output of
 >>  'locale'

 > On the currently used computer I get

 > has6121h>/.../utcke% locale
 > LANG=en_US
 > LC_CTYPE="en_US"
 > LC_NUMERIC="en_US"
 > LC_TIME="en_US"
 > LC_COLLATE="en_US"
 > LC_MONETARY="en_US"
 > LC_MESSAGES="en_US"
 > LC_PAPER="en_US"
 > LC_NAME="en_US"
 > LC_ADDRESS="en_US"
 > LC_TELEPHONE="en_US"
 > LC_MEASUREMENT="en_US"
 > LC_IDENTIFICATION="en_US"
 > LC_ALL=

 Ok.

 >>  and the raw subject header of the message as well as the Content-Type:
 >>  header.

 > Subject: =?utf-8?Q?Kartonfritze.de_-_Bestellbest=C3=A4ti?=
 >         =?utf-8?Q?gung_=28B.Nr.951-34261=29?=

 > Content-Type: text/plain;
 >         charset="utf-8"
 > Content-Transfer-Encoding: 8bit

 > Looks fine to me.

 Yes.

 >>  Ah, I only saw 'set alternates=...'. Still, the UPDATING file should
 be
 >>  read carefully before every udpate...

 > I didn't see anything in there which could be relevant.

 $assumed_charset might be.

 > What might be relevant though: depending on how I compile I might,
 > beginning with 1.5.15, see lot's of

 > Error in /afs/desy.de/user/u/utcke/.mutt/aliases, line 346: Warning: Bad
 > IDN 'aol.com' in alias 'poqet8_2'.

 > on starting, which, I believe, might also be an encoding problem...

 Ah, yes, I think I found it. First, the 'Bad IDN' usually means not
 really a bad IDN but an invalid character set (there's a bug already
 open). When looking more closely at your config, I think you got
 iconv-hook exactly the other way arround. By saying

    iconv-hook iso-8859-1 ISO8859-1

 you say that whenever mutt sees 'iso-8859-1' it should instead use
 'ISO8859-1' because the local iconv() implementation doesn't know
 'iso-8859-1' but only 'ISO8859-1'.

 The $assumed_charset changes for 1.5.15 may have cleaned things up so
 that the problem is now triggered but wasn't before.

 So, to further isolate the source, could you please a) see if the
 problem persists with 'mutt -nF /dev/null' (no config at all), and if
 not b) try removing all charset related lines ($charset, $send_charset,
 iconv-hook and charset-hook).

 Rocco
 }}}

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/2990#comment:>