BinHex - Revision history

Dexvertbot: /* Sample files */

2023-12-28T04:27:07Z

‎Sample files

Dan Tobias at 02:53, 12 May 2022

2022-05-12T02:53:50Z

Sembiance: /* Sample files */

2021-05-19T17:45:53Z

‎Sample files

Jsummers: /* Format details */

2021-01-14T16:50:06Z

‎Format details

Effect2: /* History */

2020-09-14T18:20:38Z

‎History

Effect2: Add some links

2020-09-14T18:20:18Z

Add some links

Jsummers: /* Programs and utilities */

2020-02-21T15:23:33Z

‎Programs and utilities

J2j: optional text before characteristic BinHex start line

2019-12-15T00:38:40Z

optional text before characteristic BinHex start line

Jsummers: /* Format details */

2019-09-04T17:41:36Z

‎Format details

Jsummers at 16:25, 24 November 2018

2018-11-24T16:25:10Z

@@ Line 52: / Line 52: @@
 * http://libxad.cvs.sourceforge.net/viewvc/libxad/testfiles/ASCII/hqx/
 * http://cd.textfiles.com/carousel344/MACTOSH/ → [http://cd.textfiles.com/carousel344/MACTOSH/LANG/ LANG/], [http://cd.textfiles.com/carousel344/MACTOSH/TECH/ TECH/], ...
-* https://telparia.com/fileFormatSamples/archive/binHex/
+* {{DexvertSamples|archive/binHex}}
 == References ==

@@ Line 5: / Line 5: @@
 |mimetypes={{mimetype|application/mac-binhex40}}, {{mimetype|application/mac-binhex}}, {{mimetype|application/binhex}}
 |pronom={{PRONOM|x-fmt/416}}
 |released=1981
 }}

@@ Line 51: / Line 51: @@
 * http://libxad.cvs.sourceforge.net/viewvc/libxad/testfiles/ASCII/hqx/
 * http://cd.textfiles.com/carousel344/MACTOSH/ → [http://cd.textfiles.com/carousel344/MACTOSH/LANG/ LANG/], [http://cd.textfiles.com/carousel344/MACTOSH/TECH/ TECH/], ...
 == References ==

@@ Line 34: / Line 34: @@
   !"#$%&'()*+,-012345689@ABCDEFGHIJKLMNPQRSTUVXYZ[`abcdefhijklmpqr
-which are used in that order as the digits of a base-64 representation of the binary data. There are three parts, one after another, the first being a header with file metadata, the second being the data fork, and the third the resource fork. A two-byte [[CRC]] checksum is added to each. The entire data block begins and ends with a colon (:). Lines are separated with CR every 64 characters. (This might turn into CR+LF or LF if the file is transferred across diverse systems.)
+which are used in that order as the digits of a base-64 representation of the binary data. There are three parts, one after another, the first being a header with file metadata, the second being the data fork, and the third the resource fork. A two-byte [[CRC-16|CRC]] checksum is added to each. The entire data block begins and ends with a colon (:). Lines are separated with CR every 64 characters. (This might turn into CR+LF or LF if the file is transferred across diverse systems.)
 BinHex 4 uses the [[RLE90]] compression scheme.

@@ Line 16: / Line 16: @@
 To deal with this problem, yet another version was released, called 4.0 because the author belatedly realized that other version numbers including 3.0 had been used for a different author's BinHex. This one used a different set of encoding characters, safer for transmission, and adopted the file extension '''.hqx''' which became very popular for Mac binary uploads and e-mail attachments on online services and the Internet. By then CompuServe had improved its protocols to handle raw binary files, so its utility there was lessened, but users still liked the ability to combine data and resource forks in one file (though other methods such as [[MacBinary]] were devised for this purpose).
-BinHex 5.0 used [[MacBinary]] to combine the forks of a file before encoding them in the BinHex characters, but this was not much used. Users either moved to straight MacBinary or stuck with the old, familiar BinHex 4.0, and the latter remained in use well into the 1990s.
+BinHex 5.0 used MacBinary to combine the forks of a file before encoding them in the BinHex characters, but this was not much used. Users either moved to straight MacBinary or stuck with the old, familiar BinHex 4.0, and the latter remained in use well into the 1990s.
 == Format details ==

@@ Line 46: / Line 46: @@
 * [http://www.webutils.pl/BinHex Online BinHex encoder/decoder]
 * [http://www.fpx.de/fp/Software/UUDeview/ UUDeview]
-* [http://ftp.netbsd.org/pub/pkgsrc/distfiles/macutil2.0b3.shar.Z macutil] → hexbin
+* [[macutil]] → hexbin
 == Sample files ==

@@ Line 24: / Line 24: @@
 === Version 4.0 ===
-Files are entirely in 7-bit [[ASCII]], with this first line:
+The BinHex part of the files is encoded as 7-bit ASCII.
   (This file must be converted with BinHex 4.0)
@@ Line 54: / Line 56: @@
 * [http://files.stairways.com/other/binhex-40-specs-info.txt BinHex 4.0 specs]
 * [http://www.tim-mann.org/binhex.html BinHex prehistory]
 [[Category:Archiving]]
 [[Category:Macintosh]]

@@ Line 33: / Line 33: @@
 which are used in that order as the digits of a base-64 representation of the binary data. There are three parts, one after another, the first being a header with file metadata, the second being the data fork, and the third the resource fork. A two-byte [[CRC]] checksum is added to each. The entire data block begins and ends with a colon (:). Lines are separated with CR every 64 characters. (This might turn into CR+LF or LF if the file is transferred across diverse systems.)
 == File extension ==
-The most-used version of BinHex uses the .hqx extension as noted above. Seldom-encountered earlier ones used .hex and .hcx. The .hqx extension is rather quirky for "data archeologists" because it clashes with a different convention, that of files compressed with the [[Squeeze]] protocol using file extensions with the middle letter replaced with "q". Thus, one would expect a .hqx file to be a .hex file that has been squeezed, but this is wrong; the .hqx format does not in fact have any compression (being somewhat larger than the original file rather than smaller). It's just another one of the "gotchas" that plague people who delve into old computer archives. Just what one would use as a file extension for a .hqx file that's been run through Squeeze remains unknown.
+The most-used version of BinHex uses the .hqx extension as noted above. Seldom-encountered earlier ones used .hex and .hcx. The .hqx extension is rather quirky for "data archeologists" because it clashes with a different convention, that of files compressed with the [[Squeeze]] protocol using file extensions with the middle letter replaced with "q". Thus, one would expect a .hqx file to be a .hex file that has been squeezed, but this is wrong. It's just another one of the "gotchas" that plague people who delve into old computer archives. Just what one would use as a file extension for a .hqx file that's been run through Squeeze remains unknown.
 == Programs and utilities ==