BBS:      TELESC.NET.BR
Assunto:  Differing origin lines fr
De:       Digital Man
Data:     Sat, 21 Feb 2026 17:02:00 -0800
-----------------------------------------------------------
  hbRenb: hcDiffering origin lines from Vertrauen on Dove-Net
  bBynb: hcDigital Man bto cNightfox bon cSat Feb 21 2026 04:06 pmn

 >   HBReNB: HCDiffering origin lines from Vertrauen on Dove-Net
 >   BByNB: HCDigital Man Bto CNightfox Bon CSat Feb 21 2026 03:43 pm
N >
 >  >   HBReNB: HCDiffering origin lines from Vertrauen on Dove-Net
 >  >   BByNB: HCDigital Man Bto CNightfox Bon CSat Feb 21 2026 03:32 pm
 > N >
 >  >  > Can you dump/paste the SMB header for the message and compare? Maybe
 >  >  > the entire message is the body and the tear and tag aren't going into
 >  >  > the tail? UTF-8 encoding is likely the trigger. I'll post a message
 >  >  > using UTF-8 here in a second
 >  >  > as test.
 >
 >  > Here's another reply, this time in UTF-8. Compoare those SMB headers for
 >  > me (using smbutil if need-be)?
 >
 > I think I know what's at play here. Since you said the issue does not happen
 > with the internal message reader, that's a clue: The internal message reader
 > does not word-wrap message tails (where tear/origin/tag lines normally go).
 > msglist.js doesn't read/display message tails separate from message bodies,
 > so it doesn't do that and I suspect your message reader doesn't either. So
 > that's the first difference.
 >
 > The second difference (and might be a bug) is that because the message tail
 > was UTF-8 encded, it appears the word_wrap function is miscalculating the
 > display width somewhere and inserting a line break in the middle of the
 > Vertrauen QWKnet tagline. It shouldn't be doing that either.
 >
 > So the first difference is a matter of design/opinion (should tails be
 > word-wrapped on display?) and the second is likely a bug.

So I created a small file to hopefully replicate the issue but have not been able to. Here's the file (with UTF-8 encoded high ASCII chars and Ctrl-A codes):

00000000  20 01 67 ef bf ad 01 6e  20 53 79 6e 63 68 72 6f  | .g....n Synchro|
00000010  6e 65 74 20 01 68 ef bf  ad 01 67 20 56 65 72 74  |net .h....g Vert|
00000020  72 61 75 65 6e 20 ef bf  ad 20 01 77 48 6f 6d 65  |rauen ... .wHome|
00000030  20 6f 66 20 53 79 6e 63  68 72 6f 6e 65 74 20 ef  | of Synchronet .|
00000040  bf ad 01 67 20 5b 76 65  72 74 2f 63 76 73 2f 62  |...g [vert/cvs/b|
00000050  62 73 5d 2e 73 79 6e 63  68 72 6f 2e 6e 65 74 0a  |bs].synchro.net.|

Displaying this with console.printfile() with the P_UTF8 and P_WORDWRAP flags correctly does not insert a line-break in the output to an 80-column terminal.

Are you having Vertrauen word-wrap the message bodies of posts in your downloaded QWK packets or are you (as all modern Synchronet BBSes should) doing the word-wrap on your (the QWKnet node) side? And if the latter, are you using the built-in Synchronet word-wrap functions are did you write your own?
-- 
                                            HYdigital man n(rob)

Rush quote #32:
Begging hands and bleeding hearts will only cry out for more
Norco, CA WX: 67.0F, 26.0% humidity, 1 mph SSE wind, 0.00 inches rain/24hrs
n---
  mSynchronetn  hgVertrauen n hHome of Synchronet n gh[vert/cvs/bbs].synchro.net

-----------------------------------------------------------
[Voltar]