doubly-gzipped files

doubly-gzipped files

[Alexandre Oliva]

Hi!

jka-compr is enabled by default on my site.  Whenever I save a gzipped
attachment with the extension .gz, jka-compr will gzip it at save
time, so I'll have to gunzip it twice to obtain the uncompressed
contents.  Is there any way GNUS could disable jka-compr (and any kind
of translation, for that matter) for the buffer in which it saves
files?

-- 
Alexandre Oliva  http://www.dcc.unicamp.br/~oliva  aoliva@{acm.org}
oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org.au}
Universidade Estadual de Campinas, SP, Brasil

Re: doubly-gzipped files

[Lars Magne Ingebrigtsen]

Alexandre Oliva <oliva@dcc.unicamp.br> writes:


> jka-compr is enabled by default on my site.  Whenever I save a gzipped
> attachment with the extension .gz, jka-compr will gzip it at save
> time, so I'll have to gunzip it twice to obtain the uncompressed
> contents.  Is there any way GNUS could disable jka-compr (and any kind
> of translation, for that matter) for the buffer in which it saves
> files?

Hm.  Good question.  On the one hand, it should be possible to say
that the file should be saved to "something.gz" to signal that you
want "something" to be gzipped.  But if the thing already has been
gzipped, and you just want to save it, that's not possible.  So I
don't know how to work around this problem...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: doubly-gzipped files

[Edward J. Sabol]

Excerpts from mail: (18-Nov-98) Re: doubly-gzipped files by Lars Magne Ingebrigtsen
> On the one hand, it should be possible to say that the file should be saved
> to "something.gz" to signal that you want "something" to be gzipped. But if
> the thing already has been gzipped, and you just want to save it, that's
> not possible. So I don't know how to work around this problem...

How about at least turning off jka-compr when the Content-Type is
application/x-gzip or the filename specified in the Content-Disposition ends
with ".gz"? You can do the same for uuencoded attachments where the filename
ends with ".gz" as well. That should catch just about all cases where the
problem arises.

Re: doubly-gzipped files

[Lars Magne Ingebrigtsen]

"Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:

> How about at least turning off jka-compr when the Content-Type is
> application/x-gzip or the filename specified in the Content-Disposition ends
> with ".gz"? You can do the same for uuencoded attachments where the filename
> ends with ".gz" as well. That should catch just about all cases where the
> problem arises.

If someone could suggest patches to do this, I'd apply them.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: doubly-gzipped files

[Stephen Zander]

>>>>> "Edward" == Edward J Sabol <sabol@alderaan.gsfc.nasa.gov> writes:
    Edward> How about at least turning off jka-compr when the
    Edward> Content-Type is application/x-gzip or the filename
    Edward> specified in the Content-Disposition ends with ".gz"? You
    Edward> can do the same for uuencoded attachments where the
    Edward> filename ends with ".gz" as well. That should catch just
    Edward> about all cases where the problem arises.

Could you not just check the whether the attachment is compressed by
looking at the file?  If the first two bytes are \037\213 then it's
likely that file was compressed with the gzip algorithm.  Similarly,
if the file starts with \037\235, it's likely file was compressed
using LZW (aka compress).

Checking the Content-Type is good, but determination of filetype by
extension is *evil* :)

-- 
Stephen
---
Perl is really designed more for the guys that will hack Perl at least
20 minutes a day for the rest of their career.  TCL/Python is more a
"20 minutes a week", and VB is probably in that "20 minutes a month"
group. :) -- Randal Schwartz