The only other reference I found at apple.com was this: http://developer.apple.com/documentation/MacOSX/Conceptual/BPFileSystem/ Articles/FileSystemGuidelines.html
It seems pretty explicit though: "Mac OS X uses the \n character by itself to represent the end of a line." They do go on to say that when reading files, however, applications should support \n, \r, and \n\r to promote interoperability. -- Rick Genter Principal Engineer Silverlink Communications <mailto:[EMAIL PROTECTED]> (781) 425-5763 This e-mail, including attachments, may include confidential and/or proprietary information, and may only be used by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. > -----Original Message----- > From: Matt Benson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 17, 2006 9:58 AM > To: Ant Developers List > Subject: Re: DO NOT REPLY [Bug 39585] - Core task > Condition/Os does not detect "Mac OS X" > > > ------- Additional Comments From [EMAIL PROTECTED] > > 2006-05-17 01:55 ------- > > I tried to scour the net and managed to find one > > useful reference. Of course my > > search was not exhaustive and i am not really a Mac > > developer so do not know how > > to find authoritative references. > > > > > http://developer.apple.com/technotes/tn2002/tn2065.html > > See "What are the rules for line endings?" > > They also describe the problems that will be > > encountered if UNIX-style line > > endings are not used, e.g. 'grep' returns the whole > > file content as a "matching > > line". > > > > I presume when they say "Mac-style" they mean MacOs > > prior to "Mac OS X". > > > > We have implemented a workaround by detecting 'os > > family="unix"' as per my > > Comment #4, and specifically using fixcrlf/@eol=unix > > and otherwise using fixcrlf > > with no @eol value. > > > > p.s. The initial issue Description should say: "UNIX > > LF" and the second sentence > > should be ignored. See Comment #5. > > p.p.s. You might want to change the issue Summary. > > > > Any of you OS X using Ant developers have an opinion > on this, esp. based on the link David provides above? > i.e. _should_ OS X's Unix-ness override its Mac-ness > with regard to line endings? This is actually an easy > question, come to think of it... if Java versions on > OS X continue to say that the System line.separator > property is CR, probably that's what fixcrlf should do > and we note the discrepancy in the manual. So if > someone could verify the value of line.separator on OS > X, we can probably resolve this. Assuming noone > disagrees with this means of resolving the issue. > > -Matt > > > -- > > Configure bugmail: > > > http://issues.apache.org/bugzilla/userprefs.cgi?tab=email > > ------- You are receiving this mail because: ------- > > You are the assignee for the bug, or are watching > > the assignee. > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
