Re: stats 2024 Q1

On 4/3/24 04:26, Olivier Miakinen wrote:

It is rather difficult to discuss about this format, between you who uses it and me who does not. Rather than giving examples (because they will probably be mangled), I prefer explaining the rules and how they are respected or not.

ACK
I'll say that I've been both using and advocating for foramt=flowed for many decades.
I even have a script that I run that will (re)flow content in the clipboard.
I go out of my way to use format=flowed.

1) Flowed-aware softwares (without bug) sending format=flowed Sender MUST space-stuff lines, in particular double any leading space. And lines that are too long can be breaked with soft-breaks.

I'd have to go back to RFCs to know for sure, but I think there is some criteria for when space stuffing is and is not done.
I thought, but could be misremembering, it had to do with if the previous physical line ends with a space or not.

2) Flowed-aware softwares which receive format=flowed They remove any leading space, thus undoing the space-stuff. So the lines are correctly aligned if the space-stuffing was correctly done.  And they also join lines having soft-breaks, thus reconstituting original long lines.

Same as above, I thought there was criteria for when to undo space stuffing.

3) Non flowed-aware softwares which receive format=flowed They do not remove the leading spaces, so there can be a misalignment between lines which begin with a space and lines which don't.  Also they do not join lines having soft breaks, thus mangling the expected result.

ACK

1bis) The Doctor's MesNews
The lines that are too long were breaked with soft-breaks.  But the lines beginning with a space were *not* space-stuffed.
 2bis) Flowed-aware softwares which receive The Doctor's post
The lines are correctly joined.  But there is a misalignment between lines according to the presence or absence of a leading space.

I have seen some issue related to leading spaces / space stuffing.
But that doesn't account for content that's all on a given physical line.  Admittedly the cases that I've seen in this thread are latter halfs of long lines that have been broken.  But the misalignment is within a physical line.  This is most apparent with the number of spaces around numbers in latter columns of the stats.

3bis) Non flowed-aware softwares which receive The Doctor's post
The lines are not joined, hence the big mangling.  However the identation is correct between lines according to the presence or absence of a leading space.

ACK

Final note : as you said, the lines in The Doctor's message aren't quoted, hence the rules of RFC 2646 concerning quotations are irrelevant to the bug that I pointed out.

;-)
--
Grant. . . .