Subj : Hrm...
To   : Thom Miller
From : Nightfox
Date : Wed Apr 12 2023 12:00:41

  Re: Hrm...
  By: Thom Miller to All on Wed Apr 12 2023 11:34 am

 TM> Hrm. Okay. So the 'msgtmp' that was pulled into T.A.G. on that last
 TM> message had the first few sentences as one long line with no linebreaks
 TM> (i.e. the *editor* is not inserting line breaks). In T.A.G. itself, none
 TM> of the sentences have the strange i character. In the package that's being
 TM> sent, the first few characters that I didn't manually hit 'enter' on *had*
 TM> the accented i in front of them in the packet viewer I used to examine it,
 TM> but the ones with a manual carriage return before them did not. So either

 TM> I *think* it's fastecho. As part of this 'connect old technology to new'
 TM> project, I've been working on a utility to export jam message areas to
 TM> JSON. When I run that utility and export the data from T.A.G., I'm not
 TM> seeing anything strange in the JSON file it's exporting... Curiouser and
 TM> curiouser... 

I heard that ASCII 141 (0x8D) is considered a soft-CR in FidoNet, and the echomail processor for the BBS software I'm using (Synchronet) has an option to strip those soft-CRs from incoming messages (if they're not UTF8-encoded).  I had that turned off, and I've turned that on.  So for Synchronet systems, that may be something to enable.

Nightfox
--- SBBSecho 3.20-Linux
 * Origin: Digital Distortion: digdist.synchro.net (21:1/137)

.