MSGID: 1:154/10 662569b0   
   REPLY: 2:341/234.1 66256447   
   PID: SmapiNNTPd/Linux 2.4.1   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9 2024-02-05   
   Hello Carlos,   
      
   On Mon, Apr 22 2024 00:08:32 +0000, you wrote:   
      
    NB>> Or while using HotdogEd with flowed=off, it still wraps at the 72/79   
    NB>> columns set by jam/smapinntpd, which then HotdogEd would still wrap   
    NB>> the text early because it doesn't have that many columns on the   
    NB>> screen?   
      
    CN> Yes, but it does the same with both flowed off and on (format=flowed and   
    CN> format=fixed look almost identical on readers that don't support f=f).   
    CN> If you use it in horizontal view, or on a larger screen like a tablet,   
    CN> it looks better.   
      
   Which is why I'm wondering if the wrap is set in HotdogEd for 79 characters by   
   default. Then it would obviously have that issue when using a phone with only   
   ~58 character width available.   
      
    CN> I think we had seen that tin does support f=f, at least it removed   
    CN> stuffed spaces. Does it wrap paragraphs at more than 72 chars, or are   
    CN> they adjusted to the screen width?   
      
   I tested tin on the tin nntp server that contained very old messages. However,   
   this was the only time I saw paragraphs adjusted to the screen width. Anything   
   that has come through jam/smapinntpd has been wrapped at 72-79 characters.   
      
    CN> Also, what about slrn?   
      
   I have never seen paragraphs adjusted to screen width with slrn, BUT I haven't   
   tried anything else besides jam/smapinntpd with it, either. I will have to   
   test that and see.   
      
    CN> It may be that they send paragraphs as long lines, instead of breaking   
    CN> them into several lines with soft-wrapping trailing spaces as in   
    CN> format=flowed. Smapi/JamNNTPd properly handles both formats when posting   
    CN> to the messagebase.   
      
    NB>> So is it a HotdogEd problem that you're looking to come up with a work   
    NB>> around for, specifically?   
      
    CN> No, it may be good for other newsreaders too. If I'm not mistaken,   
    CN> Smapi/JamNNTPd would work like other NNTP servers do.   
      
   I think with what I just described above (where I've seen screen width   
   paragraphs outside of jam/smapinntpd), I see now where you guys are pointing   
   out the difference against a "real" NNTP server.   
      
   Some clients probably don't understand the 'soft-wrapping trailing spaces', or   
   don't care to put them back together to re-form long lines, but can handle   
   long lines themselves just fine. Am I understanding what you are describing   
   here, now?   
      
   Regards,   
   Nick   
      
   ... Take my advice, I don't use it anyway.   
   --- slrn/pre1.0.4-9 (FreeBSD)   
    * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 15/0 90/1 103/705 105/81 106/201 120/616 123/10 124/5016   
   SEEN-BY: 128/260 135/220 225 153/757 7715 154/10 30 40 50 700 203/0   
   SEEN-BY: 218/700 220/90 221/0 6 226/30 227/114 229/110 112 113 206   
   SEEN-BY: 229/307 317 426 428 470 664 700 240/1120 5832 266/512 280/464   
   SEEN-BY: 280/5003 5555 282/1038 291/111 292/8125 301/1 310/31 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 467/888   
   SEEN-BY: 633/267 280 412 418 2744 712/848 770/1 2320/105 3634/12 5020/400   
   PATH: 154/10 280/464 633/280 229/426