The main concern is the sequence of characters used by windows to terminate a line. DOS and Windows adopted the CR+LF style, that is a carriage return followed by a line feed. In Unix notation it is the sequence \r\n.
Unix systems adopted a simple LF, that is \n. Commonly you call this a
newline character. For text files created in Windows you can use the utility
dos2unix to convert them in Unix format. See man dos2unix for details.
The presence of a carriage return triggers some common errors in BASH and other shell scripting languages. To discover the presence of \r\n in Unix or Linux you can try the
od command. Suppose you have a file containing the line "Hello world!". If it has been created in Linux you will see:
Code:
$ od -c file
0000000 H e l l o w o r l d ! \n
0000015
whereas if it has been created in Windows you will see:
Code:
$ od -c file
0000000 H e l l o w o r l d ! \r \n
0000016
See also
http://en.wikipedia.org/wiki/Newline for details about the "newline problem".