Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: Binary - ASCII difference ?
- To: tlug@example.com
- Subject: Re: Binary - ASCII difference ?
- From: Shimpei Yamashita <shimpei@example.com>
- Date: Fri, 22 Jun 2001 03:02:26 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <20010617221541.66392.qmail@example.com>; from man4u66@example.com on Sun, Jun 17, 2001 at 03:15:41PM -0700
- References: <20010617221541.66392.qmail@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <N2tQt.A.aaD.8jjM7@example.com>
- Resent-Sender: tlug-request@example.com
On Sun, Jun 17, 2001 at 03:15:41PM -0700, man4u66@example.com wrote: > hi everybody > i wanna learn what is the difference between Binary > and ASCII mode ? I faced them in gftp . > Does it matter which mode i use to download files ? > Thanks for attention.... As you may know, different operating systems use different codes to denote the end of line in ASCII files ('\n', or ASCII code 10, for UNIX; '\r', or ASCII code 13, for MacOS; and '\r\n', or ASCII code 13 followed by ASCII code 10, for DOS/Windows). The ASCII mode assumes that the file being transferred is text, and translates end-of-line characters on the fly. The problem is that this may irreparably corrupt the file if the file happens to be something besides text. If you are in doubt, it is always safer to use binary mode. At least you are guaranteed to get the file intact. -- Shimpei Yamashita http://www.shimpei.org/
- References:
- Binary - ASCII difference ?
- From: <man4u66@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: Better tell him to get his money back ( was ADSL with E-Access & GOL)
- Next by Date: Re: Compiling kterm
- Prev by thread: Re: Binary - ASCII difference ?
- Next by thread: RE: Binary - ASCII difference ?
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links