Hi, Rod.

RS> BL> BTW, how do you know where to add your EOT? Read the
RS> BL> Tear line, do you? If that's the case, what's it doing
RS> BL> that the Tear line doesn't do? Your EOT logic is loony.

RS> FM> Actually, that's a very good point. If an automated
RS> FM> process can determine where to place a SOT/EOT pair,
RS> FM> then by trivial proof a SOT/EOT pair ain't necessary.

RS> RS> You've had a brain fart. That doesnt apply to what is CREATING the
RS> message,

RS> RS> say taking what an external editor hands it as user text, bracketing
RS> RS> that with the SOT/EOT pair, and THEN doing whatever it chooses to with
RS> RS> control info outside the block of user text its not concerned with.

RS> RS> Its just as true if its got an internal editor too.

RS> FM> Yeah, I appreciate that. If you're the original creator
RS> FM> of the message you know where to stuff the SOT/EOT.

RS> And THATS what the SOT/EOT is about, the original creator
RS> of the message. Avoiding producing a message which can
RS> cause problems with stuff like embedded origin lines etc.

Yes, I know that. But...

RS> FM> But Paul is presumably doing so, by an automated
RS> FM> process (I don't *think* he's personally inside my
RS> FM> computer) in QWK2PKT, and Bob in whatever he's doing.

RS> And THATS where you are having your brain fart, thats NOT what the
RS> SOT/EOT is primarily designed to be used, so the fact that its got
RS> some blemishes in THAT situation says nothing useful whatever about
RS> whether its useful for the original creator of the message.

... I know that's the original intention. My point is, IF (and I don't
know) it is possible for a subsequent program to determine where to put
those, then they aren't necessary.

RS> So your 'isnt necessary' has imploded.

Do I make it clearer in the above?

RS> FM> And of course it maybe easier coming from QWK, if it doesn't have
RS> FM> kludge lines anyway. But hang on, I get the opinion from your current
RS> FM> discussion with Paul on this that it's not the ^a kludge lines which
RS> FM> are the problem, it's the 'text' kludge lines (like ---) which are.
RS> FM> And surely they're still a potential problem coming from QWK.

RS> Pity that if the SOT/EOT has some value with original creators of
RS> PKTs, your 'isnt necessary' has imploded tho. Its not about QWKs.

I know that, it's about PKTs.

RS> FM> SO. If it's possible for an automated process to do
RS> FM> it, it ain't necessary. Except perhaps for efficiency.

RS> Pity that thats ONLY an automated QWK/PKT convertor Frank.

Of course it is. Is it possible, in general, to scan a PKT and work out
where to put SOT/EOT? If not why not, what stuffs you up from doing
that?

RS> Says nothing useful whatever about whether its necessary
RS> for an original creator of a message in PKT format.

Which is what I'm trying to get at.

Regards, fIM.

 * * XEROX never comes up with something original
@EOT:

---