Re: OS X lineending - \n or \r
Re: OS X lineending - \n or \r
- Subject: Re: OS X lineending - \n or \r
- From: Sheehan Olver <email@hidden>
- Date: Thu, 7 Aug 2003 21:28:42 -0400
AppleWorks is still very much in a Classic mind state, even though its
carbonized (In fact, AppleWorks was already carbon before the Public
Beta was even released, and hasn't changed much since then). I would
suggest in this case either go with the classic line ending \r, which
everything mac-related should be able to read, or the windows line
ending \r\n, which gives you windows compatibility and shouldn't pose a
problem being parsed.
That being said, I believe Cocoa standardizes on \n as its line ending
for any files it creates (like property lists), and \n is probably
"the" Mac OS X line ending.
On Thursday, August 7, 2003, at 08:36 PM,
email@hidden wrote:
Date: Fri, 8 Aug 2003 01:29:14 +0200
Subject: Re: OS X lineending - \n or \r
Cc: email@hidden
To: The Amazing Llama <email@hidden>
From: "seaside.ki" <email@hidden>
Thx!
I've tried to export some file with tab-separated fields and \n as line
endings.
Using AppleWorks, I created a new database and imported the file.
AppleWorks
showed the fields correctly, but failed to find an 'end of record'
(which should be end of line).
At the end of the record an X in a square was shown (indicating Enter,
I assume). The
last column for row 1 was joined with first column of row 2.
Once I switched to \r, things worked fine.
Sure, \n SHOULD be OK. But due to the above problem, I'm no longer sure
about that....
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.