ml>> nothing... ignore all --- type lines... pass them on as they
ml>> are... do not edit/alter or change them... simple... less
ml>> thinking about whether they are tearlines or not and no time
ml>> spent coding for something that's not needed anyway...
PS>> Losing portions of messages is minor ?
ml>> who is going to loose portions of messages if the ignore the
ml>> tearline??
PE> They will be lost when exporting to a file, or converting to a
PE> format that doesn't have them specified as control lines (like
PE> FTS-4 does).
ml> what part of "IGNORE THE TEARLINE" did you not understand???!!?
Ok, I understand that part now. :-) And I see that overnight, you wish to
change VASTLY common practice, VASTLY common spec, and suddenly make
tearlines cease to exist, relegating them to user text.
ml> i repeat, "who is going to loose portions of messages if the tearline is
ml> ignored by ALL utils?"
No-one.
ml> the answer is NO ONE... yes, they may have some slight editing to do but no
Yes, you screw up 99.99% of mail, overnight.
ml> more so than what they'd normally have without some bells and whistles and
ml> other neato things...
If someone posts a C program, I get it cleanly at the moment. As any
message transport system capable of the basic fundamental requirements
would be expected to do. Except in Amateur Hour Fidonet. Where even ASCII
isn't safe. BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|