For sending to an AppleDouble un-aware system, the file was generally encoded using Base64, as opposed to being converted to AppleSingle.īefore Mac OS X, AppleSingle and Double had little presence in the Mac market, due largely to the small market share of A/UX. A MIME type was also assigned to AppleDouble, multipart/appledouble. ![]() ![]() The resource fork and Finder information, both proprietary and lacking editors under Unix, were combined into a second file. The format was later assigned the MIME type application/applefile.ĪppleDouble leaves the data fork in its original format, allowing it to be edited by normal Unix utilities. Some not-so-obvious reasons are explained in an Internet Draft. In fact, the format is so similar, it seemed there was no reason why Apple did not simply use MacBinary instead, which by that point was widely known and used. Support for the formats was later added to Unix software such as NFS and MAE, but they saw little use outside this small market.ĪppleSingle is similar in concept to the more popular MacBinary format, in that the resource and data forks are combined with a header containing the Finder information. AppleSingle combined both file forks and the related Finder meta-file information into a single file, whereas AppleDouble stored them as two separate files. ( April 2010) ( Learn how and when to remove this template message)ĪppleSingle Format and AppleDouble Format are file formats developed by Apple Computer to store Mac OS "dual-forked" files on the Unix filesystem being used in A/UX, the Macintosh platform's first Unix-like operating system. ![]() Statements consisting only of original research should be removed. Please improve it by verifying the claims made and adding inline citations. This article possibly contains original research.
0 Comments
Leave a Reply. |