A text file on Unix and a text file on Windows are basically the same. With ONE exception, for historical reasons a Windows text line ends in <CR><LF>, Carriage Return, Line Feed, while a Unix text line just ends in <LF>, Line Feed.
Lots of FTP tools like FireFTP know about this and convert automatically. Update: Oh my gosh, I must admit that even Win IE know how to do this.
I don't know how many files that you have to do this with, but say you have used binary ftp to transfer a "dos.text" to a Unix system, Open that file in vi and then save it. That blows way these <CR>'s, in Perl,'C', the \r chars away. That's it.
However normally, if you FTP in "text mode" that happens automatically in either direction for you. Or at least that is very likely. This is NOT "rocket science": to go to Unix from Windows delete the \r characters. To go from Unix to Windows, add a \r before each \n that doesn't already have a \r before it.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.