My From header causes strange effects

My From header causes strange effects

[Kai Großjohann]

My From header looks like this:

From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjoha?=
 =?iso-8859-1?q?nn?=)

This causes many followups to my messages to start with:

    Kai Großjoha nn writes

Note the superfluous space.

Also, I see "Kai Großjoha" in the summary buffer.

Somehow, I get the feeling that something is wrong here.  I'm not sure
what, however.  I think the From header encoding is syntactically
correct, by the letter of the law?

kai
-- 
I like BOTH kinds of music.

Re: My From header causes strange effects

[Matthias Wiehl]

On 25 Oct 2000, Kai Großjohann wrote:

> My From header looks like this:
> 
> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjoha?=
> =?iso-8859-1?q?nn?=)

Which is, as far as I can tell, a correctly encoded header value.

> This causes many followups to my messages to start with:
> 
>     Kai Großjoha nn writes

I've seen such an attribution in an article that was posted using
"knews".  I experienced that this program quite frequently does
strange things with article headers (especially with qp-encoded ones),
so my opinion on this would be that Gnus is not to blame here.
-- 
Matthias Wiehl <mwiehl@gmx.de> * <http://linux.unixcity.de/mwiehl/>

Re: My From header causes strange effects

[Paul Jarc]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> My From header looks like this:
> 
> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai =?iso-8859-1?q?Gro=DFjoha?=
>  =?iso-8859-1?q?nn?=)

Actually, I see it all on one line (on disk, or with C-u g), with a
space instead of the line break, in addition to the existing space.
That's not a correct unfolding of the two-line version by RFC822 -
there should be just one space, if indeed it originally was as you
said.  I don't know how those spaces should or do affect the 8859-1
decoding, though.


paul

Re: My From header causes strange effects

[Kai Großjohann]

On 25 Oct 2000, Matthias Wiehl wrote:

> I've seen such an attribution in an article that was posted using
> "knews".  I experienced that this program quite frequently does
> strange things with article headers (especially with qp-encoded
> ones), so my opinion on this would be that Gnus is not to blame
> here.

Hm.  Maybe it's all knews, but I suspect that knews is not the only
program that has problems with this encoding of my last name.  Should
we try to cater to these b0rken news readers?

Would it be better to try to find a space for breaking lines?  Though
finding a space might be hard to do, for example if there is no
space.  Hm.

kai
-- 
I like BOTH kinds of music.

Re: My From header causes strange effects

[ShengHuo ZHU]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> On 25 Oct 2000, Matthias Wiehl wrote:
> 
> > I've seen such an attribution in an article that was posted using
> > "knews".  I experienced that this program quite frequently does
> > strange things with article headers (especially with qp-encoded
> > ones), so my opinion on this would be that Gnus is not to blame
> > here.
> 
> Hm.  Maybe it's all knews, but I suspect that knews is not the only
> program that has problems with this encoding of my last name.  Should
> we try to cater to these b0rken news readers?
> 
> Would it be better to try to find a space for breaking lines?  Though
> finding a space might be hard to do, for example if there is no
> space.  Hm.

Now I improve the line-breaking algorithm a little, not breaking a QP
word which could be fitted in one line.  Hope it works for your name.

ShengHuo

Re: My From header causes strange effects

[Matthias Wiehl]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Would it be better to try to find a space for breaking lines?

Maybe, but what if knews still inserts a space then?

I mean, knews turns the line break into a space, which is apparently a
bug.  So it is possible that the space is inserted regardless of where
the encoded header is folded.

> Though finding a space might be hard to do, for example if there is
> no space.  Hm.

Yup.  One more sign of a bug in knews, IMHO.
-- 
Matthias Wiehl <mwiehl@gmx.de> * <http://linux.unixcity.de/mwiehl/>