[Prev][Next][Index][Thread]

Re: binhex/compact probs?



>Another thing you might try is simply opening the forkless files from 
>within Word.  Recently i had occasion to bring files from a NeXT where
>i had edited them under Executor, and did it via FTP which left the 
>resource fork behind (if i had used HFS_XFER and a floppy, the resource
>fork might not have been lost, i'm not sure).  Once on the Mac, though, 
>i opened Word (which you can do either by clicking on another Word file 
>or on the app itself), and used file/open (in the menu) to open the 
>forkless file.  A new resource fork must be magically created at this 
>point, because the file came up as happily as anything, formats 'n' a'.
>
>It's worth a try, at any rate.
>
>-- Maren.
>
>
>p.s.  i second the motion to digestify the list -- traffic 
>is getting up there!  A FAQ, as recently suggested, would also 
>be great, and would presumably address the issue i presented 
>not long ago (in an embarassingly-double-spaced posting caused 
>by mailing a multi-line text-file out of NeXTmail, oops!) 
>regarding a list of what works and what doesn't.  
>

This may work quite well for WORD. I have found, however, that other
applications (can't remember which ones, right now)don't necessairly work
that way. Just to give you an example.... some of the .HQX files I download
aren't recognized by the MAC and the .HQX file to be binhexed. Some of the
.HQX files can be decoded using the DOS version of Binhex.... but when the
decoded file is copied to the MAC... the MAC doesn't recognize the format of
the file. It's frustrating, to say the least.

Preston
Preston J. Tuchman
preston@indy.net