Comments on: Compression and archive formats: A description http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description The personal weblog of Peter Hosey. Tue, 07 Oct 2008 05:14:15 +0000 http://wordpress.org/?v=2.5.1 By: Domain of the Bored » Blog Archive » How to distribute your software http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-108 Domain of the Bored » Blog Archive » How to distribute your software Sun, 27 Aug 2006 08:10:25 +0000 http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-108 [...] Domain of the Bored The personal weblog of Peter Hosey, aka Mac-arena the Bored Zo. « Compression and archive formats: A description Audio version of ‘Compression and archive formats’ » [...] [...] Domain of the Bored The personal weblog of Peter Hosey, aka Mac-arena the Bored Zo. « Compression and archive formats: A description Audio version of ‘Compression and archive formats’ » [...]

]]> By: Domain of the Bored » Blog Archive » Audio version of ‘Compression and archive formats’ http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-106 Domain of the Bored » Blog Archive » Audio version of ‘Compression and archive formats’ Sun, 27 Aug 2006 08:02:26 +0000 http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-106 [...] I made my earlier blog post into a podcast. it’s just under ten minutes long, and in chaptered AAC format. have a listen. [...] [...] I made my earlier blog post into a podcast. it’s just under ten minutes long, and in chaptered AAC format. have a listen. [...]

]]> By: Mac-arena the Bored Zo http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-16 Mac-arena the Bored Zo Fri, 27 Jan 2006 21:33:00 +0000 http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-16 it was not corrected because it was already correct. see the previous paragraph: "Mac OS applications could not be transmitted over networks, because most of their essential parts were in the resource fork, which was omitted when a file was sent to another operating system or copied to another file system. StuffIt, being data-fork only, kept everything intact." there was no resource fork to preserve in a StuffIt file. it was not corrected because it was already correct. see the previous paragraph:

"Mac OS applications could not be transmitted over networks, because most of their essential parts were in the resource fork, which was omitted when a file was sent to another operating system or copied to another file system. StuffIt, being data-fork only, kept everything intact."

there was no resource fork to preserve in a StuffIt file.

]]> By: Sören 'chucker' Kuklau http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-15 Sören 'chucker' Kuklau Fri, 27 Jan 2006 10:00:00 +0000 http://boredzo.org/blog/archives/2006-01-15/compression-and-archive-formats-a-description#comment-15 "MacBinarying a StuffIt file accomplished exactly nothing: you were wrapping what was already wrapped. BinHex was useful if the file was believed likely to undergo newline conversion [..], but I think such situations were really the minority." Actually, I'm surprised nobody corrected this bit. Encapsulating a StuffIt file in MacBinary or BinHex was a means to avoid resource fork trouble. It was therefore commonly used when transferring files over the network or internet. "MacBinarying a StuffIt file accomplished exactly nothing: you were wrapping what was already wrapped. BinHex was useful if the file was believed likely to undergo newline conversion [..], but I think such situations were really the minority."

Actually, I'm surprised nobody corrected this bit. Encapsulating a StuffIt file in MacBinary or BinHex was a means to avoid resource fork trouble. It was therefore commonly used when transferring files over the network or internet.

]]>