From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Format=flowed & QP
Date: Sun, 29 Dec 2002 21:51:29 +0100 [thread overview]
Message-ID: <m3hecwlfam.fsf@defun.localdomain> (raw)
In-Reply-To: <m3adio4zah.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Jesper Harder <harder@ifa.au.dk> writes:
>
>> But maybe we shouldn't flow text at all unless the CTE is 8bit or
>> 7bit? (because QP supports soft linebreaks without f=f).
>
> I'm a bit rusty in the QP area, but I can't seem to recall any soft
> line breaks in QP... Do you have a pointer?
Well, it's not soft breaks in exactly the same sense as format=flowed.
But in QP "=" at EOL is called a soft line break. RFC 2045 section 6.7:
(5) (Soft Line Breaks) The Quoted-Printable encoding
REQUIRES that encoded lines be no more than 76
characters long. If longer lines are to be encoded
with the Quoted-Printable encoding, "soft" line breaks
must be used. An equal sign as the last character on a
encoded line indicates such a non-significant ("soft")
line break in the encoded text.
next prev parent reply other threads:[~2002-12-29 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 2:28 Jesper Harder
2002-12-29 15:31 ` Lars Magne Ingebrigtsen
2002-12-29 20:51 ` Jesper Harder [this message]
2002-12-29 22:02 ` Lars Magne Ingebrigtsen
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=m3hecwlfam.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).