Path: ...!news.misty.com!weretis.net!feeder6.news.weretis.net!tncsrv06.tnetconsulting.net!tncsrv09.home.tnetconsulting.net!.POSTED.omega.home.tnetconsulting.net!not-for-mail
From: Grant Taylor <gtaylor@tnetconsulting.net>
Newsgroups: news.admin.net-abuse.usenet
Subject: Re: stats 2024 Q1
Date: Tue, 2 Apr 2024 23:06:38 -0500
Organization: TNet Consulting
Message-ID: <uuikke$3md$3@tncsrv09.home.tnetconsulting.net>
References: <uudqvh$1fr5$1@gallifrey.nk.ca>
 <nanu.20240401124807.189@scatha.ancalagon.de> <uuepsl$v2$3@gallifrey.nk.ca>
 <uuhaeb$6sb$1@cabale.usenet-fr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Wed, 3 Apr 2024 04:06:38 -0000 (UTC)
Injection-Info: tncsrv09.home.tnetconsulting.net; posting-host="omega.home.tnetconsulting.net:198.18.1.140";
	logging-data="3789"; mail-complaints-to="newsmaster@tnetconsulting.net"
User-Agent: Mozilla Thunderbird
Content-Language: en-US
In-Reply-To: <uuhaeb$6sb$1@cabale.usenet-fr.net>
Bytes: 2855
Lines: 41

On 4/2/24 11:06, Olivier Miakinen wrote:
> The problem is with the format flowed, which makes impossible to send 
> lines of more than 79 characters as soon as they contain at least 
> one space. See <https://www.rfc-editor.org/rfc/rfc2646>.

It may be related to format flowed.  But I don't believe that format 
flowed prevents lines of more than 79 characters....  There are 
conventions about what character count on the line to do the format 
flowed split.  But a convention is a convention and can be changed. 
I've done format flowed at 25 characters and I've done format flowed at 
256 characters.

The logical line is as long as the window will support if there is 
enough source data to fill the line.

The physical line is at or below the character count as long as there is 
a space character to break / wrap the line.

> Of course, the newsreaders that are prepared (and configured to) 
> understand the format flowed don't see any problem

Um, flag on the post.  I'm using format flowed and I do see the problem.

Perhaps your algorithm is correct but the input and output is reversed?

> since it is preciseley the purpose of this format. But for older 
> newsreaders, or for users who deactivate this format they dislike, 
> the mangling is real : <https://i.goopics.net/vruq6c.png>.

That is much more severe mangling than I see.

The errors that I'm seeing aren't at the wrap point for format flowed 
either.  What I'm seeing is most evident between the 4th & 5th and the 
5th & 6th columns.  What should probably be a straight line of pipe 
characters isn't.  This is in both the format flow unwrapped logical 
line from multiple physical lines and the physical lines in the message 
source.



-- 
Grant. . . .