Re: OS X lineending - \n or \r
Re: OS X lineending - \n or \r
- Subject: Re: OS X lineending - \n or \r
- From: "seaside.ki" <email@hidden>
- Date: Fri, 8 Aug 2003 01:29:14 +0200
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....
(textfile created using ending .txt and written as ASCII text to file)
Am Freitag, 08.08.03 um 01:11 Uhr schrieb The Amazing Llama:
On Thursday, August 7, 2003, at 04:01 PM, seaside.ki wrote:
Silly question, but which characters do I have to write to a file to
generate correct
line endings?
\n is not OK.
It's not?
'\n' is the UNIX line ending. That's becoming the standard on OS X,
too, AFAIKT.
'\r' is the Classic Mac ending. Most editors will still read these.
'\r\n' is the Windows ending. That's just silly.
When is \n not OK?
Seth A. Roby The Amazing Llama < mail or AIM me at tallama at mac
dot com>
"Life is like an exploded clown. It's really funny until you figure
out what just happened."
_______________________________________________
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.