From: Russ Allbery <rra@stanford.edu>
Subject: Re: Random spaces in the subject
Date: Fri, 02 Jan 2004 14:53:30 -0800 [thread overview]
Message-ID: <8765fu7yj9.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <v9n096hu3k.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 02 Jan 2004 23:19:11 +0100")
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> If the group is nntp, I'd vote for buggy overview data (tabs, spaces,
> folding, ...) from the server. (The subjects in the summary stem from
> the overview unlike the subject in the article.)
If the Subject headers were folded, INN currently has a bug in generation
of overview for folded headers where it just replaces the CRLF with spaces
rather than unfolding the header first. (The overview specification was
iffy on what one should do.)
This will get fixed at some point.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
prev parent reply other threads:[~2004-01-02 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 2:48 Nevin Kapur
2004-01-02 22:06 ` Lars Magne Ingebrigtsen
2004-01-02 22:19 ` Reiner Steib
2004-01-02 22:40 ` Nevin Kapur
2004-01-02 22:43 ` Lars Magne Ingebrigtsen
2004-01-02 23:09 ` Nevin Kapur
2004-01-02 22:53 ` Russ Allbery [this message]
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=8765fu7yj9.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).