Subj : Re: that trick never works To : Paul Hayton From : Alan Ianson Date : Sun Apr 14 2019 19:43:48 > OK so I'm using the latest public release of Mystic and sent my original post > via 3:770/1 which we are saying is not doing anything to content. So if I > understand you right you're (and others?) are happy with the way my test post > came across to you - right? :) It looks fine here. I wish I would have grabbed that pkt before I tossed it at 757.2, But I have the message I am replying to waiting for 757.2 to pick up. Let me have a look.. Looking at the above in that pkt file there is a ^M at the end of each line. That will cause word wrapping on the readers terminal at that point. I suppose that is OK and since that is the way it originated we don't want to change any of that. Perhaps it would be a good thing if lines were not wrapped and just left as one long line until the author of the message hits the enter key? In that case the line would wrap depending on the terminal the reader is using. And of course an important detail here is not to change message content that passes through your node. It looked like some wrapping (added ^M characters) was happening at a Mystic node. Perhaps we should test that with an upto date version of Mystic and see how that goes. This is just a bit technical for me though, I think mark, Maurice and probably others can give you better information than I can. This thread might get a good going over in the FTSC_PUBLIC area? There are a large number of folks in there that could answer questions more clearly and completely than I can. > But.. we're also wondering about another system (running Mystic right? but > perhaps earlier version?) that may be adding something to the way content is > then displayed after packets pass though it. > Do I have that summarized correctly? Al? Yes, I think you are upto speed. My summary: Mystic appears to be wrapping text when the message is saved. That is best done when the message is being viewed on the readers screen. Mystic also appears to be wrapping text in messages when it tosses them on to linked nodes. Message content should not be changed in transit. --- BBBS/Li6 v4.10 Toy-4 * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757) .