Unix import of a DOS spreadsheet...

[Brian K. White]

On 9/8/2010 8:59 AM, Jeff Harrison wrote:
> --- On Tue, 9/7/10, Richard Kreiss<rkreiss at verizon.net>  wrote:
>
> [Fairlight wrote]
>
>>> Can I just be the first (and probably the last) to
>> say, "WTF?!"
>>>
>>> I honestly can't tell what you're on about, as the
>> above doesn't parse in
>> code
>>> -or- in English--at least not for me.
>>>
>>> mark->
>
>> From: Richard Kreiss<rkreiss at verizon.net>
>> Subject: RE: Unix import of a DOS spreadsheet...
>> To: "'Fairlight'"<fairlite at fairlite.com>, filepro-list at lists.celestial.com
>> Date: Tuesday, September 7, 2010, 10:34 PM
>> Mark,
>>
>> \n = ASCII 10 or NL(new Line for Unix)
>>
>> \n= ASCII 13/10 (CR\NL carriage return\New line) for
>> Windows
>>
>> Therefore \R\n on a Unix box looks for a new line for the
>> record end.
>>
>> On a Windows box \R\n import looks for a carriage return
>> and a new line
>> CR\NL
>>
>> This eliminates the byte problem on a windows box using
>> import \r.
>>
>> Richard
>>
>
> WTF?! :-)
>
> Richard, can you post some actual code to perhaps demonstrate what you are talking about?  I'm not getting it either.

Oh come on. Do any of us really not know the correct syntax for import?
Are there really any new users here who might be confused by seeing the 
wrong syntax in one email that we have to give him quite such a hard 
time? The point was just that on windows r=\n will recognize and consume 
both CR and LF bytes instead of just LF.

--
bkw