Re: bug#1660: Repyling with extended charactors in the From:
FWIW, I'm observing the same problems on a SuSE 8.1 machine myself,
but couldn't track it down so far. No problems with the Debian or
RedHat installations I normally use.
Interestingly, on the SuSE machine my editor (jed) also has problems
with Umlauts, which makes me suspect that this is some configuration
problem, and *not* a mutt bug.
--
Thomas Roessler · Personal soap box at <http://log.does-not-exist.org/>.
On 2003-10-08 11:07:56 +0200, Andrew Lunn wrote:
> From: Andrew Lunn <andrew.lunn@xxxxxxxx>
> To: 1660@xxxxxxxxxxxx, Mutt dev ml <mutt-dev@xxxxxxxx>,
> Andrew Lunn <andrew.lunn@xxxxxxxx>
> Date: Wed, 8 Oct 2003 11:07:56 +0200
> Subject: Re: bug#1660: Repyling with extended charactors in the From:
> X-Spam-Level:
>
> On Wed, Oct 08, 2003 at 01:42:56AM +0200, Alain Bench wrote:
> > [CC and MFT mutt-dev mailing list]
> >
> > Hello Andrew, thanks for your report.
> >
> > On Tuesday, October 7, 2003 at 4:45:43 PM +0200, Andrew Lunn wrote:
> >
> > > Package: Mutt=20
> > > Version: 1.5.4i
> > >
> > > I have the following email header:
> > >
> > > Subject: Re: [ECOS] Stress testing JFFS2
> > > From: \330yvind Harboe <oyvind.harboe@xxxxxxxxx>
> > > To: Andrew Lunn <andrew@xxxxxxx>
> > >
> > > Note that \330 is actually a Ö. Its a Scandinavian name.
> > >
> > > When i try to reply to this, either group or normal reply, mutt always
> > > gives me a blank To: prompt instead of giving putting the email there
> > > as it normally does. The extended character is confusing mutt.
> >
> > I full quote you because your bug report was not auto-forwarded to
> > mutt-dev, perhaps due to the mangled =20 package name. Interested people
> > can look at <URL:http://bugs.guug.de/db/16/1660.html>.
> >
> >
> > Let me try a guess: You have an UTF-8 terminal, a correctly set
> > system locale, the given char is Ø (stroked O), and the 0xD8 byte is raw
> > in header, unencoded. Right?
>
> The Ø is not raw in the header. Here is the header direct from
> /var/mail/lunn.
>
> Received: from mail.broadpark.no ([217.13.4.2])
> by londo.lunn.ch with esmtp (Exim 3.36 #1 (Debian))
> id 1A6sgV-0004CN-00
> for <andrew@xxxxxxx>; Tue, 07 Oct 2003 16:19:31 +0200
> Received: from famine (217-13-20-38.dd.nextgentel.com [217.13.20.38])
> by mail.broadpark.no (Postfix) with ESMTP id 96C1678C34
> for <andrew@xxxxxxx>; Tue, 7 Oct 2003 16:18:59 +0200 (MEST)
> Subject: Re: [ECOS] Stress testing JFFS2
> From: =?ISO-8859-1?Q?=D8yvind?= Harboe <oyvind.harboe@xxxxxxxxx>
> To: Andrew Lunn <andrew@xxxxxxx>
> In-Reply-To: <20031007141018.GD15932@xxxxxxx>
> References: <1065524219.5485.43.camel@famine>
> <20031007130402.GB15932@xxxxxxx> <1065532608.5999.8.camel@famine>
> <20031007134301.GC15932@xxxxxxx> <1065534644.5999.22.camel@famine>
> <20031007141018.GD15932@xxxxxxx>
> Content-Type: text/plain; charset=UTF-8
> Organization: Zylin AS
> Message-Id: <1065536338.6193.7.camel@famine>
> Mime-Version: 1.0
> X-Mailer: Ximian Evolution 1.4.5
> Date: Tue, 07 Oct 2003 16:18:59 +0200
> Content-Transfer-Encoding: quoted-printable
> Status: RO
> X-Status: A
> Content-Length: 1193
> Lines: 29
>
> Is the From: line correctly encoded? I don't know what RFC 2047 says.
>
> > Otherwise, if I guessed wrong, please provide us complete context
> > informations about your setup: OS, versions, iconv, terminal, charset,
> > locale, usw... So we can investigate.
>
> Debian-Testing.
> iconv (GNU libc) 2.3.2
> xterm XFree86 4.2.0(165), or xterm on SunOS 5.5. Both have the same problem.
> charset locale etc are standard defaults for Debian. Nothing special.
>
> Thanks
> Andrew
>