Subj : wrap
To   : Carlos Navarro
From : Nicholas Boel
Date : Thu Apr 04 2024 17:29:22

Hello Carlos,

On Thu, Apr 04 2024 14:19:14 +0000, you wrote:

 CN> When JamNNTPd sends to the client,
 CN> - lines that are 79 or less are not wrapped
 CN> - lines longer than 79 are wrapped by 72

 CN> Strange as it may seem, that's how format=flowed is defined in the RFC.

 CN> Nevertheless, those are the suggested values (that JamNNTPd uses). Other
 CN> numbers could be used instead, as long as they are 78 or less.

Ok. So it's doing what it should be doing, then?

 CN> The code block for format=flowed appends spaces to the end of wrapped
 CN> lines and does the 'space stuffing' at the beginning (inserts extra
 CN> space if it begins with space), as defined in the RFC.

Why would you want to stuff spaces at the beginning of a line if it starts with a space? What is the reasoning behind that?

I think the problem comes in to play with this example:

Quoting a 78 (78 is just an example, it could probably be anywhere from 74 or 75 or more characters) character line with smartquote will not reformat the line back to 78 characters (or within the 79 line width limit it should be at). It will then append the space, initials, quote character, and another space.. now making it 4 or 5 characters longer. This will then wrap the last word to the next line and it won't have a quote character in front of it.

I would imagine it would also do this without smartquote enabled, however it wouldn't add as many characters to the line, so you would see the issue less (only when a line hits 77 or 78 characters probably).

Golded seems to handle this, but Golded also seems to support displaying quoted lines longer than 79 characters, which may very well be because of the issue(s) above.

Regards,
Nick

.... Take my advice, I don't use it anyway.
--- slrn/pre1.0.4-9 (Linux)
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

.