Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Weird subject wrapping
Date: 10 Sep 2000 18:41:55 -0400	[thread overview]
Message-ID: <m3r96r27jq.fsf@multivac.student.cwru.edu> (raw)
In-Reply-To: Hannu Koivisto's message of "10 Sep 2000 19:32:56 +0300"

Hannu Koivisto <azure@iki.fi> writes:
> prj@po.cwru.edu (Paul Jarc) writes:
> 
> | RFC822 (3.1.1) says: "Unfolding is accomplished by regarding CRLF
> | immediately followed by a LWSP-char as equivalent to the LWSP-char."
> | 
> | So the leading whitespace shouldn't be removed, which means extra
> | whitespace, other than the line break, shouldn't have been inserted.
> 
> You mean "other than the line break and one space"?

No, I meant what I said.  If "foo bar" is encoded as "foo<CRLF> bar"
(only a line break is inserted, before the existing space), then it
will be decoded as "foo bar", according to RFC822.  If it is encoded
instead as "foo<CRLF>  bar" (a line break and a space are inserted),
then it will be decoded as "foo  bar".

> And, in addition, Gnus shouldn't insert extra whitespace to the
> subject display.  I.e. now, a subject that is ok by that RFC,
> 
> """
> Subject: COMMERCIAL: Extensys 1.0.1 Released. - Linux based platform for
>  developing communications applications
> """
> 
> shows in the summary buffer like this:
> 
> "...for  developing..."

Yes, there should be only one space there, according to the RFC.


paul



      reply	other threads:[~2000-09-10 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-07 22:54 Hannu Koivisto
2000-09-08  9:51 ` Kai Großjohann
2000-09-08 14:45   ` Paul Jarc
2000-09-08 15:37     ` Kai Großjohann
2000-09-08 15:45       ` Paul Jarc
2000-09-08 16:26         ` Kai Großjohann
2000-09-08 16:31           ` Paul Jarc
2000-09-10 16:32     ` Hannu Koivisto
2000-09-10 22:41       ` Paul Jarc [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=m3r96r27jq.fsf@multivac.student.cwru.edu \
    --to=prj@po.cwru.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).