You do the transfer in binary mode and what do you end up with? Utter garbage!

Incorrect. Again. What you end up with is an XML file encoded in UTF-EBCDIC.

Your supposition that your transfer tools should be able to handle all necessary conversions for you is just wrong-headed.

Let's change this assumption...

The only access available is ftp.

... and assume instead that the only available access is via a webserver.

Since it isn't going to do any conversions for you, what are you going to do? Pull out iconv, of course. Or an equivalent tool. Or do nothing so long as your tool set handles the encoding without problems.

Consider unpacking (on z/OS, if you like) an archive file containing thousands of different XML files with different encodings, created on different platforms. Then someone gives you the filename of one of those and tells you they need you to transfer it to a totally different platform. Whatchagonnado?

I'll gift you a hint. Under ASCII mode [. . . snip . . .]

And I've already gifted you the hint: don't use ASCII mode.

Update:

The point of ASCII mode, is that the source encodes the data into a known format: "8-bit NVT-ASCII". At the destination, that format is then converted to whatever local format is required. The point of this is that each system only needs to know how to convert from its local format and the "well-known format".

You know, that whole paragraph explains a lot. Are you perhaps just so steeped in the old ways of doing things that you completely fail to recognize what advantages a universal cod(e)ing imparts and the problems it solves?

-sauoq
"My two cents aren't worth a dime.";

In reply to Re^20: Native newline encoding by sauoq
in thread Native newline encoding by salva

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.