This actually bit me at work recently. I ran a command in powershell, and redirected the output to create a text file. On windows, looked fine. On OS X, looked fine. Sent it off to a Gentoo Linux box, and things barfed, as it claimed it was a binary file. Looked deeper, and Powershell created a UTF-16 file, with a BOM marker, set to little endian. The Gentoo box didn't like it.

First CR/LF nightmares, and now UTF madness. For basic "text". ugg.