home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!news.univie.ac.at!chx400!bernina!bernina!neeri
- From: neeri@iis.ethz.ch (Matthias Neeracher)
- Subject: Re: Why does BinHex exist? (my mistake)
- In-Reply-To: howard@netcom.com's message of Fri, 8 Jan 1993 18:04:38 GMT
- Message-ID: <NEERI.93Jan12113717@iis.ethz.ch>
- Sender: news@bernina.ethz.ch (USENET News System)
- Organization: Integrated Systems Laboratory, ETH, Zurich
- References: <2965@tau-ceti.isc-br.com> <C0JD83.DMz@news.cso.uiuc.edu>
- <1993Jan8.180438.9696@netcom.com>
- Date: Tue, 12 Jan 1993 10:37:17 GMT
- Lines: 24
-
- In article <1993Jan8.180438.9696@netcom.com>, howard@netcom.com (Howard Berkey) writes:
-
- > I should have made it clear that I know what binhex actually does.
- > My mistake was in assuming that everyone would be able to
- > have access to uuencode, which does substantially what binhex does
- > (i.e. convert a binary file to 7-bit (6 for binhex but the same
- > principle)) so it can be mailed/cross EBCDIC gateways/etc.).
-
- BinHex preserves file types and both forks of a file, while uuencode
- doesn't. Otherwise, they are pretty similiar (And no, I don't think
- uuencode uses 7 bits, it creates files that are bigger than BinHex files).
- So even if everybody had access to uuencode, I don't see a particularly good
- reason to use it.
-
- My preferred solution would be to store files in MacBinary on servers, but
- make the ftp daemon translate files to BinHex if requested (Peter Lewis' ftpd
- does this, if I remember correctly).
-
- Matthias
-
- -----
- Matthias Neeracher neeri@iis.ethz.ch
- "You must have picked up that copy of Scarlett instead of Inside Mac
- when you tried to find the right call..." -- Keith Rollin
-