RE: Unix file to PC, weird LF-CR

Hmmm.  Wordpad is *not* handling this file correctly.  If it matters, I'm
told that we get the file zipped from the Unix shop and we unzip it here.
Could it be that the Unix zip / Windoze unzip is not converting the LF or CR
character correctly?

- Dan Bale

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Adam Lang
Sent: Thursday, February 14, 2002 1:36 PM
To: midrange-l@midrange.com
Subject: Re: Unix file to PC, weird LF-CR


It is because Microsoft "embraced and extended" end of lines.  Unix only
uses one character to end lines (either LF or CR ... can not recall).  Goofy
assed MS uses CRLF to denote end of line.

If you open the unix text file in wordpad, it handles the the unix style
correctly.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Dan Bale" <dbale@samsa.com>
To: <midrange-l@midrange.com>
Sent: Thursday, February 14, 2002 1:34 PM
Subject: Unix file to PC, weird LF-CR


> Anybody know about how Unix does Line Feeds and Carriage Returns?  We've
got
> a file from a Unix system that we want to load to the 400.  On our Windoze
> PC, the "records" of data all show up on one line.  I recognize that this
is
> a stream file, but there's a funny looking character at the end of each
> "record".  If I can determine the hex value of that LF-CR character, is
> there a way to import the stream file from the PC to an AS400 file on a
V3R2
> system that does not have Client Access?
>
> TIA,
> - Dan Bale