Subj : Squish Compatability Fix
To   : apam
From : Oli
Date : Mon Dec 11 2023 11:38 am

apam wrote (2023-12-10):

 >> 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.

 a> Squish stores most kludges seperately from the message text (all but
 a> seenby and path).

 a> The fix only changes the way talisman stores them in the squish base.
 a> Prior to the fix messages exported from talisman would have carraige
 a> returns added, and imported messages would have carriage returns removed
 a> for storage.

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:

<SOH>CHARSET: LATIN1<SOH>REALNAME: Mark Twain<NUL>

It seems the previous behavior was correct. I also cannot find any CR between control items in sqd files that were created by Squish (the tosser) on Linux.

 a> The issue occured when using a particular third party on bases created by
 a> talisman, it was expecting a carriage return to signify the end of the
 a> kludge line and did stupid things when it didn't get one.

Which software is that?

 a> Although now that you mention it, I suppose it could be seen as all in
 a> the message body / text as the the control body is right before the
 a> message body in the squish structure - and that makes sense, hmm.

 a> looks like it's also not supposed to have a carriage return after the
 a> last kludge :(


⁂

---
 * Origin: No REPLY kludge - no reply (21:3/102)

.