Re: stats 2024 Q1

Le 03/04/2024 06:19, Grant Taylor a écrit :

On 4/2/24 11:52, Olivier Miakinen wrote:

Actually, it seems that there is also a (lesser) problem that only affects
the newsreaders which accept the format flowed, because apparently your
MesNews did not do the "space-stuffing" :
<https://www.rfc-editor.org/rfc/rfc2646#section-4.4>
 
<cit. (only the first characters of the lines)>
  num| Name                                                     | Nb Msg |
----|----------------------------------------------------------|--------|
   1 | Adam H. Kerman                                           |     78 |
</cit.>

 
This more aptly describes what I'm seeing.
 
My news reader does format flowed.
 

In format flowed, the space before "num" should have been doubled, and the
two spaces before "1" should have been three. Indeed, this indentation
stays correct for those who don't accept format flowed for reading, but
for the others it will be rendered shifted :
 
<ex.>
num| Name                                                     | Nb Msg |
----|----------------------------------------------------------|--------|
  1 | Adam H. Kerman                                           |     78 |
</ex.>

 
I want to agree, but I think what you say is contrary to section 4.4 of
RFC 2646 which you linked to.

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.


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.

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.

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.


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.

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.


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.


Best Regards,
--
Olivier Miakinen