Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!archimedes.math.uwm.edu!jgreco
From: jgreco@archimedes.math.uwm.edu (Joe Greco)
Newsgroups: comp.sys.cbm
Subject: Re: (repost) FTP Help
Message-ID: <2692@uwm.edu>
Date: 2 Mar 90 04:54:04 GMT
References: <13380.25ed5b44@max.u.washington.edu>
Sender: news@uwm.edu
Organization: University of Wisconsin, Milwaukee - Dept of Mathematics
Lines: 17

In article <13380.25ed5b44@max.u.washington.edu> scott@max.u.washington.edu writes:
>With Kermit, it always advisiable to always set the file type to binary
>since there is no drawback even when you are transfering ascii files.

What about end-of-line character translation?  Please, give me  a break.

I'm sure Kermit isn't going to adjust the UNIX style ^J end of line marker
to a more standard ^M if you set it to binary.  Ever tried working with a file
with all ^J's in it on a Commodore?  You can't print it... hard to read... at
least on UNIX you could send it through "tr".

As for FTP file mode, there I've always set it to binary even for ASCII files.
This has never created any  problems for me, but I only transfer from UNIX
to UNIX and occasionally a Sperry 1100.  It seems to produce more overhead
in binary mode than ASCII.  I don't know details.
 
... Joe