TID: FMail-W64 2.3.2.2-B20240419   
   TZUTC: 0200   
   CHRS: UTF-8 4   
   MSGID: 2:341/234.1 6627cb9a   
   REPLY: 1:154/10 662569b0   
   21 Apr 2024 14:32, you wrote to me:   
      
    CN>> Yes, but it does the same with both flowed off and on   
    CN>> (format=flowed and format=fixed look almost identical on readers   
    CN>> that don't support f=f). If you use it in horizontal view, or on   
    CN>> a larger screen like a tablet, it looks better.   
      
    NB> Which is why I'm wondering if the wrap is set in HotdogEd for 79   
    NB> characters by default. Then it would obviously have that issue when   
    NB> using a phone with only ~58 character width available.   
      
   No. It's just that it doesn't support f=f's soft wraps. A "real" long line is   
   wrapped at screen width.   
      
    CN>> I think we had seen that tin does support f=f, at least it   
    CN>> removed stuffed spaces. Does it wrap paragraphs at more than 72   
    CN>> chars, or are they adjusted to the screen width?   
      
    NB> I tested tin on the tin nntp server that contained very old messages.   
    NB> However, this was the only time I saw paragraphs adjusted to the   
    NB> screen width. Anything that has come through jam/smapinntpd has been   
    NB> wrapped at 72-79 characters.   
      
   So it has partial f=f support, as it seems it doesn't recognize soft wraps.   
      
    NB>>> So is it a HotdogEd problem that you're looking to come up with   
    NB>>> a work around for, specifically?   
      
    CN>> No, it may be good for other newsreaders too. If I'm not   
    CN>> mistaken, Smapi/JamNNTPd would work like other NNTP servers do.   
      
    NB> I think with what I just described above (where I've seen screen width   
    NB> paragraphs outside of jam/smapinntpd), I see now where you guys are   
    NB> pointing out the difference against a "real" NNTP server.   
      
    NB> Some clients probably don't understand the 'soft-wrapping trailing   
    NB> spaces', or don't care to put them back together to re-form long   
    NB> lines, but can handle long lines themselves just fine. Am I   
    NB> understanding what you are describing here, now?   
      
   Yes!   
   Thunderbird and Seamonkey do, but most others don't.   
      
   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 256 1124 467/888 633/280 712/848 770/1 5020/400 5054/30   
   PATH: 341/234 280/464 460/58 229/426