• Subject: RE: Last symbol in doc after cpytopcd
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Tue, 09 Jan 2001 10:25:55 -0800
  • Organization: Pacer International

That ASCII 26 character is, indeed, the end of file character, and
will be written for any TEXT file on a PC, as it is required to know
the end of the text document.  And each text file can only have one
EOF (End of File ASCII 26) character.  If there is one in the middle
of the file, any text editor will only load the document to that point.

Binary files, however, do not require the EOF marker on the end, as 
ASCII 26 is a legitimate character for binary data.  The length of binary
data is handled different ways, usually by a file header that specifies
the length of the actual data.  The file length you see for any PC file
is actually the number of bytes taken up on the disk by the file, not the
actual file length (the last sector would have unused section on the end).

Sooo... You are going to have to write this file in binary mode instead of
text mode.  One way I could think of doing this, is by translating the file
from EPISODIC to ASCII.  Then FTP this file to the PC using BINARY mode 
(type BINARY in the FTP client before you transmit the file).  This would
require a lot of headache and translation on your part, however.

My question is, why do you need to write at TEXT file without the EOF marker
and last Carriage Return/Line Feed pairs?  I know in one PC program I wrote
at one time I had problems with this too, as every time I saw a CR/LF pair
I assumed I was going to get the next record, then the next record was blank
(just the EOF).  I decided to accept the CR/LF as the END of my text line and
when I went to read a line looking for the EOF marker.  If the EOF was there,
I was done.


Jim Langston

From: KOKOREV@conversbank.ru [mailto:KOKOREV@conversbank.ru]
Sent: Tuesday, January 09, 2001 7:21 AM
To: MIDRANGE-L@midrange.com
Subject: Last symbol in doc after cpytopcd

Any more suggestions?
Thank in advance.

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.