Open behdad opened 8 years ago
If you are talking about legacy "Mac OS" CR Line Endings, no, this won't work.
From gitattributes(5):
eol (core.eol)
This attribute sets a specific line-ending style to be used in the working directory. It enables end-of-line normalization without any content checks, effectively setting the text attribute.
Set to string value "crlf"
This setting forces Git to normalize line endings for this file on checkin and convert them to CRLF when the file is checked out.
Set to string value "lf"
This setting forces Git to normalize line endings to LF on checkin and prevents conversion to CRLF when the file is checked out.
So only DOS/Typewriter (CRLF) and Unix (LF) line endings are supported. OS X uses Unix line endings though, and so does Linux.
Looking at https://github.com/Monotype/OpenType_Table_Source/blob/gh-pages/downloads/chainedcoverage.txt tells me that GitHub doesn't support CRs quite well either.
Looks like there is nothing about line endings in the spec either, so I guess changing CR to LF or CRLF is still valid for the spec?
Looks like there is nothing about line endings in the spec either, so I guess changing CR to LF or CRLF is still valid for the spec?
I believe so.
So, converting to Unix line endings for sample files would be best perhaps?
There's a way to tell git that they are text files I believe. https://help.github.com/articles/dealing-with-line-endings/