TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Paul Edwards
from: Bob Lawrence
date: 1996-06-15 10:54:20
subject: 4x16meg Simms 4 Sale

BL> And nowhere in any FTS document does it specify I must *not*
 BL> type #1EOT in the text window. 

 PE> This is the last time I take the effort to quote what you can
 PE> easily see for yourself. 

 PE> If the first character of a physical line (e.g. the first
 PE> character of the message text, or the character immediately
 PE> after a hard carriage return (ignoring any linefeeds)) is a ^A
 PE> (, 01H), then that line is not displayed as it
 PE> contains control information. The convention for such control
 PE> lines is:

  Although you did not say it, this is FTS-1 under the heading:
Message Text.

  Where does it say I can't enter #1 in text? It merely says: "then
that line is not displayed." In fact, it infers that #1 *may* be sent
in normal text.

  Nowhere does it say: "#1 must be removed from message text if if it
is not a defined control line..." or anything vaguely like that.

  Nowhere does it say: "#1 must be translated to another character if
entered by the user..."

  There are simple reasons why it *cannot* say that. How do you know
where user text begins and ends? How do you know what is a control
line keyword?

  You are reading meanings into FTS-1 that are not there.

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---
* Origin: Precision Nonsense, Sydney (3:711/934.12)
SEEN-BY: 711/934
@PATH: 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.