home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   JAMNNTPD      Support for the JAMNNTPD software client      2,630 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 2,546 of 2,630   
   Carlos Navarro to Nicholas Boel   
   space oddity (fixes)   
   21 Apr 24 21:08:32   
   
   TID: FMail-W64 2.3.2.1-B20240412   
   TZUTC: 0200   
   CHRS: UTF-8 4   
   MSGID: 2:341/234.1 66256447   
   REPLY: 1:154/10 6623f2e2   
   20 Apr 2024 11:52, you wrote to me:   
      
    NB>>> Wouldn't '/nowrap' just be 'flowed=on', which would then leave   
    NB>>> the formatting to HotdogEd, which doesn't seem to be doing so   
    NB>>> properly?   
      
    CN>> HotdogEd (like may other newsreaders) doesn't support   
    CN>> format=flowed, so it doesn't join the wrapped lines with trailing   
    CN>> space.   
      
    NB> So, if HotdogEd doesn't support format=flowed, wouldn't it be better   
    NB> to use 'flowed=off'?   
      
   In principle it would be better, like with any newsreader that doesn't support   
   f=f, so that stuffed spaces are not displayed. Other than that, there should   
   be no difference.   
      
   In HotdogEd it doesn't really matter, as it doesn't display consecutive spaces   
   e.g. used for indentation (you can't view ASCII art properly unless you select   
   "View raw article").   
      
    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?   
      
   Yes, but it does the same with both flowed off and on (format=flowed and   
   format=fixed look almost identical on readers that don't support f=f). If you   
   use it in horizontal view, or on a larger screen like a tablet, it looks   
   better.   
      
    NB> Both of these look fine on Thunderbird (with flowed=on), as well as   
    NB> tin (with flowed on and off), and slrn (with flowed on), and I'm still   
    NB> unsure format=flowed is supported in either of the last two mentioned.   
      
   I think we had seen that tin does support f=f, at least it removed stuffed   
   spaces. Does it wrap paragraphs at more than 72 chars, or are they adjusted to   
   the screen width?   
      
   Also, what about slrn?   
      
    NB> Maybe tin and slrn can deal with incoming format=flowed, but just   
    NB> don't post that way..?   
      
   It may be that they send paragraphs as long lines, instead of breaking them   
   into several lines with soft-wrapping trailing spaces as in format=flowed.   
   Smapi/JamNNTPd properly handles both formats when posting to the messagebase.   
      
    NB> So is it a HotdogEd problem that you're looking to come up with a work   
    NB> around for, specifically?   
      
   No, it may be good for other newsreaders too. If I'm not mistaken,   
   Smapi/JamNNTPd would work like other NNTP servers do.   
      
   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   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca