Thanks for the feedback.
Funny, though. I don't remember asking for it to be posted to this
In article <mpro.lhs8lk00001fm05hc.pittdj(a)pittdj.co.uk>, David Pitt
application/zip Archive a91 .zip
which needs to be :-
application/zip Zip a91 .zip
Okay, that change makes sense and will be made to the file for the next
Do you think I should change the catch-all zip entry too, or didn't you
look that far?
Perhaps consider that .zip .arc and for that matter .cab are all
classified as Archive types in the pee sea and the official Acorn
position used to be that many types (.ARJ, .GZ, .HPK, .HQX, .LHA, .LZH,
.SIT, .SPK, .UU, .ZIP or .ZOO ) were included in &DDC as a result. That
and the problem that .arc files used not to be recognised by some web
servers so knowing all Archive types were DDC anyway, .arc files would be
called .zip instead so they would download. Uploaders didn't always think
to call them leafname.arc.zip though, which may have saved me a few
headaches in the past.
This is partly why a mimemap file may need to be tailored for each
system. It is unlikely there will ever be one size fits all. Your
software and ability will determine your needs but then so will any file
you may try and download tomorrow. I try to keep my mimemap up-to-date so
as not to be surprised, even if I download, say, an .flv or .docx file.
We used to suffer many comments on c.s.a.usenet along the lines of "I
have downloaded a file with extension .xxx but it is typed 000 and
appears as a white square. I can't get it to run [etc]". Having a mimemap
file as up-to-date-as possible will avoid such confusion. Beware some
people who operate on the "wait 'til it breaks then fix it" paradigm.
They just like telling you what to do when it does. :-)
You managed to email me last year when you had a suggestion about
mimemap, I'm not sure why you thought it necessary or appropriate to rant
in semi-public and give Druck the chance to whinge. ;-)
Sorry, this is my last posting on the topic here.