Further: Do ftp apps remove resource forks?

Basically, all non-Mac systems do not support resource forks, and most file transfer protocols (including FTP, SFTP, WebDAV, Amazon S3) do not support resource forks, therefore there are three possible options:

A) Strip the resource fork and just send the data fork
B) Encode the file in MacBInary or some other format
C) Send the data fork and send the resource fork (and optionally other meta data) in a secondary format.

For most Mac files, especially for most modern Mac files, the resource fork and meta data is optional and adds only peripherally to the file, so A is normally the preferred choice for most FTP transfers.

Encoding in MacBinary is very limited, it includes only a small subset of meta data, and is limited to 2GB (possibly 4GB) data and resource fork lengths, 63 character file name (with no encoding specified), etc.

If you upload a jpg/png/gif file in MacBinary encoding to a web site, you will find that it doesn't work and your images all display as broken links.

WebDAV (including iDisk) and some other Apple programs use method C, storing the AppleDouble data in a file named ._filename. Whether this is good or bad depends very much on what exactly you are trying to do.

BTW, Interarchy 8.0 dropped support for MacBinary (essentially because it caused more problems than it solved), however Interarchy 8.2 added support for transparent file converters, and include both a MacBinary encoder, as well as a Backup encoder which encodes all meta data (including things like HFS+ extended attributes) and has none of the limitations of MacBinary.

Enjoy,
   Peter.

--
Check out Interarchy 8.2, just released, now with Growl support.
<http://www.stairways.com/>  <http://download.stairways.com/>

--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
If so, please send mail to <[EMAIL PROTECTED]>, not to the list.
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>
To unsubscribe, send mail to:  <[EMAIL PROTECTED]>

Reply via email to