Received: by 10.68.222.71 with SMTP id qk7mr5343623pbc.1.1328943705418;
        Fri, 10 Feb 2012 23:01:45 -0800 (PST)
MIME-Version: 1.0
Path: wr5ni11406pbc.0!nntp.google.com!news1.google.com!news.glorb.com!usenet.stanford.edu!not-for-mail
From: Eli Zaretskii <e...@gnu.org>
Newsgroups: gnu.emacs.help
Subject: Re: ange-ftp using binary mode
Date: Sat, 11 Feb 2012 09:01:12 +0200
Lines: 17
Approved: help-gnu-em...@gnu.org
Message-ID: <mailman.3665.1328943704.15002.help-gnu-emacs@gnu.org>
References: <jh43p6$gfu$1@dough.gmane.org>
NNTP-Posting-Host: lists.gnu.org
X-Trace: usenet.stanford.edu 1328943705 17894 140.186.70.17 (11 Feb 2012 07:01:45 GMT)
X-Complaints-To: action@cs.stanford.edu
To: help-gnu-em...@gnu.org
Envelope-to: help-gnu-em...@gnu.org
In-reply-to: <jh43p6$gfu$1@dough.gmane.org>
X-012-Sender: ha...@inter.net.il
X-detected-operating-system: by eggs.gnu.org: Solaris 10 (beta)
X-Received-From: 80.179.55.166
X-BeenThere: help-gnu-em...@gnu.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Users list for the GNU Emacs text editor <help-gnu-emacs.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-gnu-emacs>,
	<mailto:help-gnu-emacs-requ...@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/help-gnu-emacs>
List-Post: <mailto:help-gnu-em...@gnu.org>
List-Help: <mailto:help-gnu-emacs-requ...@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-gnu-emacs>,
	<mailto:help-gnu-emacs-requ...@gnu.org?subject=subscribe>

> From: Ken Goldman <kg...@watson.ibm.com>
> Date: Fri, 10 Feb 2012 16:55:49 -0500
> 
> I have to use ange-ftp because the server I'm connecting to doesn't run 
> ssh.  When I transfer, it uses binary, which does not work.  The server 
> is a mainframe and likely uses ebcdic.

Are you using ange-ftp via "C-x C-f"?  If so, tell Emacs to decode the
file, as in "C-x RET c ebcdic-us RET C-x C-f whatever RET".

If you use some other command, again prefix that command with
universal-coding-system-argument ("C-x RET c") to tell it to use
EBCDIC, or whatever is right for those files.

IOW, just imagine the file was on your local disk, and do the same.
You cannot tell disk I/O to "use ascii", can you?