[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ProgSoc] jpg file
On Fri, Mar 13 1998, Christian Kent wrote:
|
| On Fri, 13 Mar 1998, rsu@nospam.acs.itd.uts.edu.au wrote:
|
| > i've got a mac-binhex40 jpg file in my dir. i cannot seem to view it
| > through the web. do i have to convert to something else? what do i have to
| > do?
|
| Get Stuffit Expander from aladdinsys.com. This is just an encapsulation
| made by a brain-dead Mac user who goes back to the days when every time
| you transferred something over the net it was 7-bit.
Whoever invented binhex was no more brain-dead than the person who
invented UUENCODE.
Why didn't they just re-use the UUENCODE format? Actually, the issue is
more complex with Macintosh files, because Mac files are made up of 1 or
more "forks", and each fork of a file is processed differently. What
corresponds to the "content" of a file goes into the data fork, while
configuration information and things such as the file's icon (unlike
Windows and Unix, individual Mac files can have their own icon) goes
into the resource fork. Other forks can be available.
Admittedly JPEG files have little use of their resource fork, so a
straight binary format would have been more useful. If you use Stuffit
Expander for Windows, configure it to discard the resource forks of
files.
PS. There's an 8-bit equivalent of BinHex, called MacBinary... I still
use BinHex sometimes tho as I can't split large binary files to fit on
floppies and re-merge them (easily) on a Mac.
Cheers,
--
Dennis Clark dbugger@nospam.progsoc.uts.edu.au PGP/MIME spoken here
-------------------------------------------------------------------------------
If you think the system is working, ask someone who's waiting for a prompt.
PGP signature