Your best friend for file transfer.

Fetch application logoFetch

file types (2 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 21 years ago by egghead
  • Latest reply 21 years ago from Jim Matthews
  • egghead Member


    I just noticed something odd when trying to upload/download files without suffixes to/from a UNIX server.

    If I start with a BBEdit text file on my Mac, it gets uploaded correctly as a text file. However, if I want to download it and get a BBEdit text file back, the only way seems to be to check the "automatic defaults to text" box in the download prefs, and then map all text files to BBEdit.

    This set up has the following disadvantage: if I upload an Appleworks file without a suffix, eg, a file called test; then it will be uploaded as a MacBinary file, but downloaded as a BBEdit file called test, which then gets decoded as the Appleworks file test.1

    I don't see how to make sure that both types of files are correctly handled. I can arrange for the Appleworks file to be correctly downloaded by unchecking the "automatic defaults to text" box, but then the BBEdit files come back as generic binary documents.

    Any idea how to solve this would be welcome. (I suppose i could just bite the bullet and use suffixes: anyone know the one for Appleworks?)

    Personally, I'd be happy just to use MacBinary in both directions, as only use the server as a storage space, and don't care so much about line endings on text files being converted.

    Posted 21 years ago #

  • Jim Matthews Administrator

    It would certainly work to do your up and downloading in MacBinary format -- that will preserve type/creator information (which in turn indicates the icon to use). Otherwise you need to store the file type information in the file name, i.e. as a file name suffix.


    Jim Matthews
    Fetch Softworks

    Posted 21 years ago #

Topic closed

This topic has been closed.