>   
>
> Thanks for looking into this, David! And for your tips about submitting 
> file formats.
>
 

> For the extra information for the PRONOM entry:
>
>  

> The official mimetype is  listed  
> <http://www.iana.org/assignments/media-types/application/applefile>as 
> *application/applefile*
>
>  

> *Description*:
>
> Apple Computers created the AppleSingle format (as well as the AppleDouble 
> format) to represent and preserve the attributes of files across files 
> systems that do not support the same attributes of the file’s home systems. 
> AppleSingle is primarily a storage format and contains both a file’s 
> contents and attributes. It consists of a header and one or more optional 
> data entries followed by the byte stream of the file it is storing. It 
> maintains the original Macintosh filename and file type(ie. Mydoc.pdf). The 
> AppleSingle format can store a number of different kinds of formats. 
>
  

> *Specific to AppleSingle v2*:  AppleSingle 2.0 is a revision to the 
> original AppleSingle specification, in that it replaced and added some data 
> entry fields
>
> <https://tools.ietf.org/html/rfc1740>
>
> *Release*: 1990
>
>  

> *Developed by*: Apple Computers
>
>  

> *Documentation*: https://tools.ietf.org/html/rfc1740 
> http://apple2online.com/web_documents/ft_e0.0001_applesingle.pdf 
> http://macjournals.com/special/AppleSingle-Double.pdf 
>
>  
>
> *Signature description*: 
>
> BOF: “….....” 4 byte AppleSingle Magic Number, followed by 4 byte version 
> number 
>
>  
>
> I’m still doing some research on the format, and would be happy to flesh 
> the entry out more if needed. 
>
 

> Andy Jackson was kind enough to search the UK Web Archive for files that 
> include the AppleSingle magic number. Because of ANZ proxy stuff, I’ve been 
> unable to download the entire payload so far, but I have a few more 
> examples (that aren’t pdf!) I can share from that collection.  As far as 
> I know from what I’ve read and looked at, the relationship is 1:1.
>
>  
>
> MacBinary does look tricky, and I was going to try and tackle that next. I 
> have a few examples from the govdocs corpus, and the spec for macbinary II 
> (http://files.stairways.com/other/macbinaryii-standard-info.txt)says: 
>
>  
>
> It is possible to write a much more robust routine, by checking the
>
> following:
>
>   Offsets 101-125, Byte, should all be 0.
>
>   Offset 2, Byte, (the length of the file name) should be in the range of 
> 1-63.
>
>   Offsets 83 and 87, Long Word, (the length of the forks) should be in the
>
>     range of 0-$007F FFFF
>
>  
>
> So… fun! I’ll try and take a look into that 'BinHex Binary Text' format, 
> too. These Apple header type files are a rabbit hole I’m happy to fall into.
>

Attachments: 

   -  CSV of files from the UK Web Archive that have the AppleSingle magic 
   number
   - A pch, mpe and bin file with the AppleSingle header
   - Two PDFs with the macbinary header