Hi
Today I pushed a fix for Talisman squish message bases to work better
with other squish software.
I did not realize that control lines are seperated by carraige returns,
and so have added that.
IIRC control (kludge) lines are part of the message body / text and
should be stored unmodified. Is the fix only related to control lines
that are created by Talisman or did the bug also affect control lines
from imported messages? I'm just curious.
IIRC control (kludge) lines are part of the message body / text and
should be stored unmodified. Is the fix only related to control lines
that are created by Talisman or did the bug also affect control lines
from imported messages? I'm just curious.
Squish stores most kludges seperately from the message text (all but
seenby and path).
The fix only changes the way talisman stores them in the squish base.
Prior to the fix messages exported from talisman would have carraige returns added, and imported messages would have carriage returns removed for storage.
The issue occured when using a particular third party on bases created by talisman, it was expecting a carriage return to signify the end of the kludge line and did stupid things when it didn't get one.
Although now that you mention it, I suppose it could be seen as all in
the message body / text as the the control body is right before the
message body in the squish structure - and that makes sense, hmm.
looks like it's also not supposed to have a carriage return after the
last kludge :(
Looks like I didn't remember it correctly. According to the "Squish Developers Kit (Version 2.00)" documentation there is no CR after a
control item. They are separated by SOH (0x01) only. Example from the
spec:
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 06:40:15 |
Calls: | 500,305 |
Calls today: | 6 |
Files: | 95,205 |
D/L today: |
382 files (92,297K bytes) |
Messages: | 465,500 |