Subj : wrap
To   : Nicholas Boel
From : Carlos Navarro
Date : Wed Apr 03 2024 11:02:00

02 Apr 2024 19:48, you wrote to Tommi Koivula:

 TK>> So, IMHO the "hard wrap" setting WRAP_WIDTH 72 is not working as
 TK>> it should with "flowed on". I think Jamnntpd should adjust the
 TK>> WRAP_WIDTH setting according to the "flowed" setting and not wrap
 TK>> lines with "flowed on".

 NB> If I'm understanding you correctly, WRAP_WIDTH should remain 72 only
 NB> when 'def_flowed=off', and when 'def_flowed=on' it should be disabled
 NB> completely? If that's the case, I agree.

In format=flowed, long lines are wrapped but they have a trailing space. The client, if it supports this format, joins the lines, showing them as a paragraph.

From RFC-2646:
---------------------------------
Generating Format=Flowed

When generating Format=Flowed text, lines SHOULD be shorter than 80
characters.  As suggested values, any paragraph longer than 79
characters in total length could be wrapped using lines of 72 or
fewer characters.  While the specific line length used is a matter of
aesthetics and preference, longer lines are more likely to require
rewrapping and to encounter difficulties with older mailers.  It has
been suggested that 66 character lines are the most readable.

(The reason for the restriction to 79 or fewer characters between
CRLFs on the wire is to ensure that all lines, even when displayed by
a non-flowed-aware program, will fit in a standard 80-column screen
without having to be wrapped.  The limit is 79, not 80, because while
80 fit on a line, the last column is often reserved for a line-wrap
indicator.)

When creating flowed text, the generating agent wraps, that is,
inserts 'soft' line breaks as needed.  Soft line breaks are added
between words.  Because a soft line break is a SP CRLF sequence, the
generating agent creates one by inserting a CRLF after the occurance
of a space.
---------------------------------

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
 * Origin: cyberiada (2:341/234.1)

.