From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: My From header causes strange effects
Date: 25 Oct 2000 23:45:16 +0200 [thread overview]
Message-ID: <vafu2a0389f.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <873dhlc67f.fsf@fulmine.dhs.org>
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.
next prev parent reply other threads:[~2000-10-25 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-25 12:09 Kai Großjohann
2000-10-25 15:04 ` Matthias Wiehl
2000-10-25 21:45 ` Kai Großjohann [this message]
2000-10-25 23:06 ` ShengHuo ZHU
2000-10-27 22:35 ` Matthias Wiehl
2000-10-25 15:48 ` Paul Jarc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafu2a0389f.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).