AppleDouble
(Added Kaitai Struct link) |
|||
| Line 2: | Line 2: | ||
|formattype=electronic | |formattype=electronic | ||
|subcat=Archiving | |subcat=Archiving | ||
| + | |extensions={{ext|adf}}, others/special | ||
|mimetypes={{mimetype|multipart/appledouble}} | |mimetypes={{mimetype|multipart/appledouble}} | ||
|pronom={{PRONOM|fmt/966}}, {{PRONOM|fmt/503}} | |pronom={{PRONOM|fmt/966}}, {{PRONOM|fmt/503}} | ||
|kaitai struct=apple_single_double | |kaitai struct=apple_single_double | ||
| + | |released=1990 | ||
}} | }} | ||
[[AppleDouble]] is one of the systems used to store the [[Resource Fork]] of Macintosh files on filesystems not natively supporting it, something which became necessary when Apple moved to Unix-based operating systems instead of "classic" MacOS. [[AppleSingle]] is an alternative format to accomplish the same end, combining all the forks plus a metadata header in one file instead of keeping separate files like AppleDouble. While both AppleSingle and AppleDouble were introduced for use with early Unix-based Apple systems, AppleDouble survived as the main method of storing files with resource forks on OS X systems if a filesystem is used that doesn't directly support such forks. | [[AppleDouble]] is one of the systems used to store the [[Resource Fork]] of Macintosh files on filesystems not natively supporting it, something which became necessary when Apple moved to Unix-based operating systems instead of "classic" MacOS. [[AppleSingle]] is an alternative format to accomplish the same end, combining all the forks plus a metadata header in one file instead of keeping separate files like AppleDouble. While both AppleSingle and AppleDouble were introduced for use with early Unix-based Apple systems, AppleDouble survived as the main method of storing files with resource forks on OS X systems if a filesystem is used that doesn't directly support such forks. | ||
| − | The AppleDouble format keeps the data fork of the file in its original format and filename (this is the main file, as used by non-Mac operating systems, and for many file formats, the only one that matters), and creates a second file with the resource fork as well as Finder metadata | + | == File naming == |
| + | The AppleDouble format keeps the data fork of the file in its original format and filename (this is the main file, as used by non-Mac operating systems, and for many file formats, the only one that matters), and creates a second "header" file with the resource fork as well as Finder metadata. | ||
| − | == | + | The specification says that the header filename should be prefixed with a "%", or prefixed with "R.", or have a file extension of ".ADF", depending on the filesystem's capabilities. |
| + | |||
| + | However, in the OS X era, the convention is to prefix the header filename with "._" (a dot and an underscore). | ||
| + | |||
| + | Sometimes, instead of using a different filename, the header files are put in special subdirectories named ".AppleDouble". | ||
| + | |||
| + | == Identification == | ||
| + | AppleDouble header files begin with signature bytes (hex) {{magic|00 05 16 07}}. | ||
| + | |||
| + | == Specifications == | ||
* [http://kaiser-edv.de/documents/AppleSingle_AppleDouble.pdf File format details] | * [http://kaiser-edv.de/documents/AppleSingle_AppleDouble.pdf File format details] | ||
* RFC 1740 (describes various Mac-specific formats) | * RFC 1740 (describes various Mac-specific formats) | ||
== Metaformat files == | == Metaformat files == | ||
| − | * {{Synalysis| | + | * {{Synalysis|appledouble}} |
== Utilities == | == Utilities == | ||
| Line 29: | Line 41: | ||
[[Category:Macintosh]] | [[Category:Macintosh]] | ||
[[Category:Filesystem]] | [[Category:Filesystem]] | ||
| + | [[Category:Multi-file formats]] | ||
Revision as of 16:16, 14 February 2019
AppleDouble is one of the systems used to store the Resource Fork of Macintosh files on filesystems not natively supporting it, something which became necessary when Apple moved to Unix-based operating systems instead of "classic" MacOS. AppleSingle is an alternative format to accomplish the same end, combining all the forks plus a metadata header in one file instead of keeping separate files like AppleDouble. While both AppleSingle and AppleDouble were introduced for use with early Unix-based Apple systems, AppleDouble survived as the main method of storing files with resource forks on OS X systems if a filesystem is used that doesn't directly support such forks.
Contents |
File naming
The AppleDouble format keeps the data fork of the file in its original format and filename (this is the main file, as used by non-Mac operating systems, and for many file formats, the only one that matters), and creates a second "header" file with the resource fork as well as Finder metadata.
The specification says that the header filename should be prefixed with a "%", or prefixed with "R.", or have a file extension of ".ADF", depending on the filesystem's capabilities.
However, in the OS X era, the convention is to prefix the header filename with "._" (a dot and an underscore).
Sometimes, instead of using a different filename, the header files are put in special subdirectories named ".AppleDouble".
Identification
AppleDouble header files begin with signature bytes (hex) 00 05 16 07.
Specifications
- File format details
- RFC 1740 (describes various Mac-specific formats)
Metaformat files
- Synalysis grammar file (for Hexinator / Synalize It!; more details)
