REPLYADDR tommi@rbb.homeip.net
REPLYTO 2:221/10.0 UUCP
MSGID:  80ea8487
REPLY:  eeb0f58c
BBSID: LCCSG
PID: SoupGate-Linux v1.23 20240225
CHRS: UTF-8 4
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:115.0) Gecko/20100101 
  Thunderbird/115.9.0
Content-Type: text/plain; charset=UTF-8; format=flowed
From: Tommi Koivula 

On 31.03.2024 23:20, Carlos Navarro wrote:

>
>>> I've found that JamNNTPd wraps at 72 chars in all lines except
>>> the last one, that can be up to 79 chars.
>
> TK> Yes, and it seems that it always wraps the text it shows to the
> TK> client. Defined by WRAP_WIDTH in nntpserv.c.
>
> JamNNTPd always sends wrapped text. If flowed=on, it will append a
> space to the end of each wrapped line. It's up to the client (if it
> supports format=flowed) to re-join those lines and show it as a
> paragraph.

I did some research between Jamnntpd and a "real" nntp server, like this
WendzelNNTPd, which I'm writing now from.

Jamnntpd with "flowed on": Flowed text in TB does not work ok when
resizing window.

WendzelNNTPd : Flowed text work ok when resizing window.

However, in this server the Content-Type line has no "format=" part at all:

   Content-Type: text/plain; charset="iso-8859-1"

So, IMHO the "hard wrap" setting WRAP_WIDTH 72 is not working as it
should with "flowed on". I think Jamnntpd should adjust the WRAP_WIDTH
setting according to the "flowed" setting and not wrap lines with
"flowed on".

'Tommi

--- 
 * Origin: LCC SG - Linux 6.1.21-v7+ armv7l (2:221/10)
SEEN-BY: 15/0 90/1 103/705 105/81 106/201 124/5016 128/260 135/220
SEEN-BY: 135/225 153/757 7715 154/10 30 203/0 218/700 840 221/1 6
SEEN-BY: 221/10 242 360 226/30 227/114 229/110 112 113 206 307 317
SEEN-BY: 229/426 428 470 664 700 240/1120 5832 266/512 280/464 5003
SEEN-BY: 280/5555 282/1038 291/111 292/8125 301/1 310/31 320/219 322/757
SEEN-BY: 335/364 341/66 234 342/200 396/45 423/81 120 460/58 256 1124
SEEN-BY: 467/888 633/280 712/848 770/1 5020/400 1042 5054/30
PATH: 221/10 6 1 280/464 460/58 229/426