From: Simon Josefsson <jas@extundo.com>
Subject: Re: format=flowed not respected
Date: Wed, 22 Oct 2003 08:31:21 +0200 [thread overview]
Message-ID: <iluptgpvl52.fsf@extundo.com> (raw)
In-Reply-To: <874qy2wk5b.fsf@doohan.bang.priv.no> (Steinar Bang's message of "Tue, 21 Oct 2003 19:55:12 +0200")
Steinar Bang <sb@dod.no> writes:
>>>>>> Simon Josefsson <jas@extundo.com>:
>
>> So Opera is breaking a SHOULD in RFC 2646 when it does not break the
>> lines before the 80th column. Gnus is behaving correctly in this
>> example, as far as I can tell.
>
> But the broken SHOULD isn't the culprit, right? If the lines in
> questions had had a trailing space, Gnus would have broken them?
No, the receiving MUA only flow lines together, it doesn't break
lines.
E.g. if you receive
foo barSPC
baz fooSPC
bar
Gnus would flow that together into
foo bar baz foo bar
I don't recall the specification saying anything about breaking (even
overlong) lines, at the receiving end.
next prev parent reply other threads:[~2003-10-22 6:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 10:00 Steinar Bang
2003-10-21 11:10 ` Simon Josefsson
2003-10-21 17:55 ` Steinar Bang
2003-10-22 6:31 ` Simon Josefsson [this message]
2003-10-22 19:58 ` Steinar Bang
2003-10-23 5:29 ` Simon Josefsson
2003-10-23 6:53 ` Steinar Bang
2003-10-23 7:07 ` Simon Josefsson
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=iluptgpvl52.fsf@extundo.com \
--to=jas@extundo.com \
/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).