|go ahead... be a heretic|
Re^19: Native newline encodingby BrowserUk (Pope)
|on May 29, 2012 at 13:03 UTC||Need Help??|
The point is: don't use FTP to to transfer XML files in ASCII mode as they may or not be ASCII encoded.
You really don't have a clue do you.
Let's posit a scenario. There is an XML file on a z/OS system that you need to transfer to your *nix system. The only access available is ftp. You do the transfer in binary mode and what do you end up with? Utter garbage! Because it is encoded in UTF-EBCDIC and is now totally unintelligible.
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".
I'll gift you a hint. Under ASCII mode, if the source file is not actually ASCII encoded, the ftp protocol requires that it be converted to ASCII -- or, in this era of unicode, an "ASCII compatible format" like UTF-8 -- for transmission.
If the source file is in EBCDIC, the it is converted to ASCII (or an ASCII compatible) format.
If the source file is in UTF-EBCDIC, then it is converted to ASCII (or an ASCII compatible) format.
Seeing the pattern yet?
Go away, and read the RFC -- I mean actually read it -- and then just stay stum.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.