If the Net::FTP module handles the ASCII transfer mode, it should be able to request it of the server for those files which need it. Then one side strips out carriage returns in transit. That's what it's for. BINARY mode keeps both sides' bytes intact, which sounds like what's happening for you.

Cygwin has a setting for whether or not the programs will work with \x0D\x0A or \x0A as the default value for \n. I don't know whether you've looked into that, or if it's something you can change in your circumstances.

--
[ e d @ h a l l e y . c c ]

In reply to Re: Cygwin perl... ftp... Windows line endings... by halley
in thread Cygwin perl... ftp... Windows line endings... by boston_guy1

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.