gnupic: Re: SOLUTION: How to use MPASM generated "cod" files with GPSIM
Subject:
Re: [PIC]: SOLUTION: How to use MPASM generated "cod" files with
GPSIM
From:
Alex Holden ####@####.####
Date:
15 Sep 2000 21:50:48 -0000
Message-Id: <Pine.LNX.4.04.10009152229500.572-100000@hyperspace.linuxhacker.org>
On Fri, 15 Sep 2000, Wojtek Zabolotny wrote:
> # Note: Compression schemes like "gzip", "bzip", and "compress" are not
> # actually "mime-types". They are "encodings" and hence must _not_ have
> # entries in this file to map their extensions. The "mime-type" of an
> # encoded file refers to the type of data that has been encoded, not the
> # type of the encoding.
That's not how the mime types are conventionally used though. Consider
what would happen, for example, if a web server sent the mime type
text/plain for gzip encoded text files (according to the above comment,
the data that has been encoded is text, so that's what the mime type
should be). The browser would display the binary file as if it was a text
file instead of asking for a location to save it as you would expect...
> So what should I set to get the "application/x-gunzip" type for ".gz" files?
I wouldn't bother. application/octet-stream is just as valid for gzip
files as application/x-gzip or application/x-gunzip (it's basically a
generic "any binary data" type). I've trimmed down the mimeremove rules a
lot so a lot of things that previously would have got stripped (including
application/octet-stream) will now get through.
--
--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------
