Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!udel!burdvax!dvnspc1!gary
From: gary@dvnspc1.Dev.Unisys.COM (Gary Barrett)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Text file conversion between UNIX and MSDOS
Message-ID: <368@dvnspc1.Dev.Unisys.COM>
Date: 17 Feb 89 19:12:43 GMT
References: <89Feb9.123853est.2662@godzilla.eecg.toronto.edu>
Distribution: na
Organization: Unisys Corporation, Devon, PA
Lines: 35

In article <89Feb9.123853est.2662@godzilla.eecg.toronto.edu>, noworol@eecg.toronto.edu (Mark Noworolski) writes:
> Very frequently when I get stuff off the net I run into the problem of
> no carriage returns. It appears that UNIX stores text a little differently
> from Messdos.
> 
> Bafore writing something to fix this problem... I figure somebody's probably
> already done it.
> 
> Can somebody send me a program to do this?
> mark
> 
> -- 
> There's a really fine line between stupid and clever.
> 
> 	Nigel - Lead Guitar, Spinal Tap
> 
> noworol@ecf.toronto.edu

There is indeed a fine line.

This problem(?) is not restricted to MS-DOS versus UNIX.  Nor is it
restricted to CR/LF versus LF.  There are a number of machines still
in existence which identify end-of-line as a single CR.  The problem
is historic.   It is also related to how teletypes and printers used
to (still do) interpret the ASCII control characters during a print
operation.


Nonetheless, you are in luck with regard to
CR/LF <-> LF translation.  Most file transfer utilities
allow you to customize ASCII transfer sessions such that end-of-lines will 
be magically converted just fine. Check the program you are using.
You may already have the capability.   Otherwise, check into getting a
shareware version of Procomm.    I think that it provides that
capability.