DT> Squish thinks that ASCII 95 is the correct character to use in the
DT> tear, that would explain why it's adding one even if there's a
DT> previous (ASCII 45) tear in the message, added buy GOldED+ - if
DT> Squish is looking for three 95 chars and what's there is 3 45
DT> chars.
FWIW: here's all your control lines above and below so you can see exactly what
is getting out here to the rest of the network ;)
DT> There's no GoldED+ tear in the messages I'm sending out because
DT> I've configured GoldED+ to not add one - I don't want to end up
DT> with two, which is what was happening when I was testing.
two tearlines, while not "pretty" is not bad, either... but your GoldED is
using the PID since you've turned off the tearline stuff... PIDs and tearlines
with text are a nono according to the PID/TID spec...
DT> Thanks for your help, I'll see what I can figure out.
might need the squish sources and apply some code fixing so it'll either
recognize the PID and add an empty tearline or it'll use the TIP instead and
have an empty tearline... then one might also add the option to specify
stripping the tearline since they are not required by the spec ;)
DT> ___ Squish/386 v1.11
DT> - Origin: � Almost At The Top Of The Hill � Newfane, VT USA �
DT> (1:132/505)
the above modified automatically when quoted... the tearline is now three
underscores instead of dashes... the asterisk in the origin line is now a
single dash... my editor, TimED, does this automatically so that brain dead
tossers don't get confused...
