TID: FMail-W64 2.3.1.0   
   TZUTC: 0200   
   CHRS: UTF-8 4   
   MSGID: 2:341/234.1 660e709d   
   REPLY: 1:154/10 660dda52   
   03 Apr 2024 17:38, you wrote to me:   
      
    CN>> In format=flowed, long lines are wrapped but they have a trailing   
    CN>> space. The client, if it supports this format, joins the lines,   
    CN>> showing them as a paragraph.   
      
    NB> I understand this. However, what Tommi and I are discussing is that   
    NB> jamnntpd/smapinntpd is not doing this properly. I'm not sure   
    NB> 'WRAP_WIDTH 72' is very constant, as I see wrapping all over the place   
    NB> between 72-79 characters (which sometimes even wraps a word to the   
    NB> next line and doesn't include a quote character before it). So either   
    NB> the 'WRAP_WIDTH 72' and 'LINE_WIDTH 79' settings are messing with each   
    NB> other, or they're not implemented properly.   
      
   When JamNNTPd sends to the client,   
   - lines that are 79 or less are not wrapped   
   - lines longer than 79 are wrapped by 72   
      
   Strange as it may seem, that's how format=flowed is defined in the RFC.   
      
   Nevertheless, those are the suggested values (that JamNNTPd uses). Other   
   numbers could be used instead, as long as they are 78 or less.   
      
   BTW, JamNNTPd uses these same values also for format=fixed. Not a big issue   
   IMO, but it could be changed so that it uses a different value in this case.   
      
    NB> So, in my questions to Tommi, I'm more or less asking if anyone has   
    NB> actually figured out what WRAP_WIDTH is actually doing. It is only   
    NB> checked for once in the code, and so is LINE_WIDTH. Neither of them   
    NB> are checked for in the format=flowed section. It almost seems like the   
    NB> format=flowed section was an afterthought, and was added in after what   
    NB> it was already doing. *shrug*   
      
   The code block for format=flowed appends spaces to the end of wrapped lines   
   and does the 'space stuffing' at the beginning (inserts extra space if it   
   begins with space), as defined in the RFC.   
      
   Carlos   
      
   --- GoldED+/W32-MSVC 1.1.5-b20180707   
    * Origin: cyberiada (2:341/234.1)   
   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 221/0 6 226/30   
   SEEN-BY: 227/114 229/110 112 113 206 307 317 426 428 470 664 700 240/1120   
   SEEN-BY: 240/5832 266/512 280/464 5003 5555 282/1038 291/111 292/8125   
   SEEN-BY: 301/1 310/31 320/219 322/757 341/66 234 342/200 396/45 423/120   
   SEEN-BY: 460/58 467/888 633/267 280 412 418 2744 712/848 770/1 5020/400   
   PATH: 341/234 280/464 633/280 229/426