🚀 go-pugleaf

djk@boombox.apana.org.au (David Keegel) writes:

>Strangely enough, on Unix (where C was developed), this text conversion
>is a no-op; like converting to network byte order on a Sun.

>So the question is whether the file in question is a text file or a
>binary file.  If it is a text file, it should obey local conventions.
>In the case of MS-DOS, it should have \015\012 (\r\n) separated lines,
>and a \032 (^Z) character denoting EOF, which is of course stripped.

>I think a news item is (should be) a text file.

>Perhaps we should be complaining about Waffle not translating the ^Z
>into something innoculous when it *writes* the file (when \n -> \r\n
>is done) rather than when it *reads* the file.

>But then tell me, what is the MS-DOS convention for quoting a ^Z?
>Answer: none.  If there was one, the compiler writers could implement
>it as an extra translation for text files (eg: when writing text
>^Z --> ???; like \n --> \r\n).  Then the applications wouldn't need
>to worry about this rubbish.

Or just pick up a copy of "Strip", and have it *remove* the ^Z characters
from the files. 

-- 
Leonard Erickson		      leonard@qiclab.scn.rain.com
CIS: [70465,203]			 70465.203@compuserve.com
FIDO:   1:105/51	 Leonard.Erickson@f51.n105.z1.fidonet.org
(The CIS & Fido addresses are preferred)