Resource Fork - Revision history

Ross-spencer: Added link to Tyler's talk on resource forks

2023-03-08T13:02:42Z

Added link to Tyler's talk on resource forks

Jsummers at 17:32, 17 November 2018

2018-11-17T17:32:33Z

Jsummers at 14:36, 6 October 2018

2018-10-06T14:36:21Z

Jsummers at 17:44, 26 December 2015

2015-12-26T17:44:56Z

Jsummers: Updated links

2015-04-08T02:10:08Z

Updated links

Dan Tobias at 03:58, 24 October 2013

2013-10-24T03:58:44Z

Dan Tobias at 03:58, 24 October 2013

2013-10-24T03:58:30Z

Dan Tobias at 03:57, 24 October 2013

2013-10-24T03:57:32Z

Dan Tobias at 03:25, 23 October 2013

2013-10-23T03:25:55Z

Dan Tobias at 19:13, 8 February 2013

2013-02-08T19:13:58Z

@@ Line 15: / Line 15: @@
 == References ==
 * [[Wikipedia:Resource fork|Resource fork (Wikipedia)]]
 See also [[Macintosh resource file#References]].
 [[Category:File format details]]
 [[Category:Macintosh]]

← Older revision		Revision as of 17:32, 17 November 2018
Line 10:		Line 10:

	Later (Unix-based) Mac systems used [[AppleSingle]] and [[AppleDouble]] formats instead of the "classic" resource fork format when using filesystems not supporting direct use of resource forks. This usage continues in some OS X filesystems.		Later (Unix-based) Mac systems used [[AppleSingle]] and [[AppleDouble]] formats instead of the "classic" resource fork format when using filesystems not supporting direct use of resource forks. This usage continues in some OS X filesystems.
		+
		+	Other methods of storing a resource fork on a foreign filesystem include [[MacBinary]] and [[BinHex]].

	== References ==		== References ==

@@ Line 3: / Line 3: @@
 |subcat=Filesystem
 }}
-Pre-OS X and some OS X Macintosh files have two forks: the data fork, and the '''resource fork''', which is subdivided into resources. Many file formats use the resource fork to store data, stored in [[Macintosh resource file]] format.
+:''This article is about the concept of a Macintosh resource fork, and the methods of storing it. For the usual '''file format''' used by a resource fork, see [[Macintosh resource file]].''
-A resource has a [[FourCC|four-character type code]], an ID, and data. The type code is generally unique to the type of data stored within, but this may not be the case with application-specific formats.
+Pre-OS X and some OS X Macintosh files have two forks: the data fork, and the '''resource fork''', which is subdivided into resources. Many file formats use the resource fork to store data, stored in [[Macintosh resource file]] format.
 Resource forks are usually invisible to the end-user on a Mac platform, but when Mac files are placed in a medium where users of other operating systems can see them (e.g., Windows), they are often visible as an additional subdirectory called '''resource.frk''', or else a name with an underscore (_) as its first character (e.g., _MACOSX for OS X files) containing subdirectories and files that parallel the structure of the files they are associated with.
@@ Line 13: / Line 13: @@
 == References ==
 * [[Wikipedia:Resource fork|Resource fork (Wikipedia)]]
-* [http://developer.apple.com/legacy/mac/library/documentation/mac/pdf/MoreMacintoshToolbox.pdf More Macintosh Toolbox] (format is described on page 1-121 to 1-125)
+See also [[Macintosh resource file#References]].
-* [https://github.com/kreativekorp/ksfl KSFL] reads and writes Macintosh resource files
-* [https://github.com/kreativekorp/ksfl/wiki/Macintosh-Resource-File-Format Description of the file format] from the KSFL wiki
 [[Category:File format details]]
 [[Category:Macintosh]]

@@ Line 5: / Line 5: @@
 Pre-OS X and some OS X Macintosh files have two forks: the data fork, and the '''resource fork''', which is subdivided into resources. Many file formats use the resource fork to store data, stored in [[Macintosh resource file]] format.
-A resource has a four-character type code, an ID, and data. The type code is generally unique to the type of data stored within, but this may not be the case with application-specific formats.
+A resource has a [[FourCC|four-character type code]], an ID, and data. The type code is generally unique to the type of data stored within, but this may not be the case with application-specific formats.
 Resource forks are usually invisible to the end-user on a Mac platform, but when Mac files are placed in a medium where users of other operating systems can see them (e.g., Windows), they are often visible as an additional subdirectory called '''resource.frk''', or else a name with an underscore (_) as its first character (e.g., _MACOSX for OS X files) containing subdirectories and files that parallel the structure of the files they are associated with.

@@ Line 12: / Line 12: @@
 == References ==
-* [http://en.wikipedia.org/wiki/Resource_fork Resource fork (Wikipedia)]
+* [[Wikipedia:Resource fork|Resource fork (Wikipedia)]]
 * [http://developer.apple.com/legacy/mac/library/documentation/mac/pdf/MoreMacintoshToolbox.pdf More Macintosh Toolbox] (format is described on page 1-121 to 1-125)
-* [http://code.google.com/p/ksfl/ KSFL] reads and writes Macintosh resource files
+* [https://github.com/kreativekorp/ksfl KSFL] reads and writes Macintosh resource files
-* [http://code.google.com/p/ksfl/wiki/MacintoshResourceFileFormat Description of the file format] from the KSFL wiki
+* [https://github.com/kreativekorp/ksfl/wiki/Macintosh-Resource-File-Format Description of the file format] from the KSFL wiki
 [[Category:File format details]]
 [[Category:Macintosh]]

@@ Line 11: / Line 11: @@
 Resource forks are usually invisible to the end-user on a Mac platform, but when Mac files are placed in a medium where users of other operating systems can see them (e.g., Windows), they are often visible as an additional subdirectory called '''resource.frk''', or else a name with an underscore (_) as its first character (e.g., _MACOSX for OS X files) containing subdirectories and files that parallel the structure of the files they are associated with.
-Later (Unix-based) Mac systems used [[AppleSingle]] and [[AppleDouble]] formats instead of the "classic" resource fork format.
+Later (Unix-based) Mac systems used [[AppleSingle]] and [[AppleDouble]] formats instead of the "classic" resource fork format when using filesystems not supporting direct use of resource forks. This usage continues in some OS X filesystems.
 == References ==

← Older revision		Revision as of 03:25, 23 October 2013
Line 10:		Line 10:

	Resource forks are usually invisible to the end-user on a Mac platform, but when Mac files are placed in a medium where users of other operating systems can see them (e.g., Windows), they are often visible as an additional subdirectory called '''resource.frk''', or else a name with an underscore (_) as its first character (e.g., _MACOSX for OS X files) containing subdirectories and files that parallel the structure of the files they are associated with.		Resource forks are usually invisible to the end-user on a Mac platform, but when Mac files are placed in a medium where users of other operating systems can see them (e.g., Windows), they are often visible as an additional subdirectory called '''resource.frk''', or else a name with an underscore (_) as its first character (e.g., _MACOSX for OS X files) containing subdirectories and files that parallel the structure of the files they are associated with.
		+
		+	Later (Unix-based) Mac systems used [[AppleSingle]] and [[AppleDouble]] formats instead of the "classic" resource fork format.

	== References ==		== References ==

← Older revision		Revision as of 19:13, 8 February 2013
Line 5:		Line 5:


−	Pre-OS X and some OS X Macintosh files have two forks: the data fork, and the resource fork, which is subdivided into resources. Many file formats use the resource fork to store data.	+	Pre-OS X and some OS X Macintosh files have two forks: the data fork, and the resource fork, which is subdivided into resources. Many file formats use the resource fork to store data, stored in [[Macintosh resource file]] format.

	A resource has a four-character type code, an ID, and data. The type code is generally unique to the type of data stored within, but this may not be the case with application-specific formats.		A resource has a four-character type code, an ID, and data. The type code is generally unique to the type of data stored within, but this may not be the case with application-specific formats.