On Thu 21 Nov 2024 at 10:11:56 (+0700), Max Nikulin wrote:
> On 20/11/2024 22:20, Greg Wooledge wrote:
> > Content-Type: text/plain; charset=us-ascii
> 
> > On Wed, Nov 20, 2024 at 10:13:20 -0500, eben wrote:
> 
> > > Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> > > This line has one trailing space.
> [...]
> >    This line has two leading and two trailing spaces.
> 
> I think, format=flowed is important here. It may be disabled in
> Thunderbird, but it may interact with line width limit and in some
> cases it might be necessary to explicitly wrap lines ([Ctrl+R] for
> selection). Flowed format allows readers to rewrap paragraphs to
> smaller width (unfortunately Thunderbird rewraps even to fill really
> wide windows).

AFAICT, Gene's post: https://lists.debian.org/debian-user/2024/11/msg00522.html
looks like a well-formed f=f post, complete with signature. The
web version referenced here shows flowing in action when you change
the font size, /but/ it does strip the space in the signature
separator.

John's reply: https://lists.debian.org/debian-user/2024/11/msg00535.html
has interpreted Gene's f=f text, and he reports that signature
stripping worked. However, the post itself uses very long f=fixed
lines, making no attempt to reflow the text into shorter lines.

Gene's response: https://lists.debian.org/debian-user/2024/11/msg00537.html
appears to do everything correctly, reflowing the quote and flowing
Gene's text. Assuming it stripped the signature automatically, Gene's
version wins.

Eben also replied to the first post with:
https://lists.debian.org/debian-user/2024/11/msg00555.html
but TB's action here show a very odd interaction between f=f and
quoted-printable. Gene's text is reflowed, but to a linelength that
causes most lines to be split a few characters from the end by q-p,
and these lines are now written as f=fixed (no space at the end).
Eben's text is ambiguous, but I suspect the last paragraph was
typed on two lines.

So my guess is that Eben's entire post is stripped of trailing spaces,
likely by a q-p encoder that enforces a 74-char line length but is
unaware of both format=flowed text and signature separators.

Cheers,
David.

Reply via email to