Some gzip implementations include incorrect filenames

[GoogleCodeExporter]

What steps will reproduce the problem?
1. unzip attached file (hd93521_032_01_a_ph.fits.gz) with Unarchiver

What is the expected output? What do you see instead?
Expect, based on filename, to get file hd93521_032_01_a_ph.fits.  That is
the file produced by BOMArchiveHelper.app or gunzip at command line. 
Instead, The Unarchiver.app produces hd93521_032.01_a_ph_fits

What version of the product are you using? On what operating system?
OS X 10.4.11, Unarchiver 1.6.1

Please provide any additional information below.
7zx.app produces same (wrong) filename as Unarchiver...

Original issue reported on code.google.com by nathanie...@gmail.com on 22 Aug 2008 at 1:39

Attachments:

• hd93521_032_01_a_ph.fits.gz

[GoogleCodeExporter]

Original comment by paracel...@gmail.com on 5 Nov 2008 at 2:10

• Changed state: Accepted

[GoogleCodeExporter]

After taking a closer look at the file, "hd93521_032.01_a_ph_fits" is 
technically the
correct filename to output. Gzip files can contain the filename of the original 
file,
and this one does, and for this one it is set to exactly 
"hd93521_032.01_a_ph_fits".

Of course, for the user this is not very useful. I'm not sure if this can or 
should
be fixed, however, as it would have to mean always ignoring the included 
filename.

The real problem here is that the program that produced the file in the first 
place
is buggy, and is creating files with the wrong filename.

It seems gzip itself ignores the filename included in the file, however. I am 
really
not sure what to do about this one.

Original comment by paracel...@gmail.com on 27 Nov 2008 at 12:26

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by paracel...@gmail.com on 14 Dec 2008 at 8:20

• Changed title: Some gzip implementations include incorrect filenames

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

You could include an option (maybe just using 'defaults write') to emulate gzip 
bugs.
Alternatively you could try to detect a contradiction between actual filename 
and the
stored filename and offer a dialog similar to the one used to select a 
character set.

Original comment by jarvik7 on 22 May 2009 at 1:33

[GoogleCodeExporter]

Original comment by paracel...@gmail.com on 20 Jul 2009 at 4:25

• Added labels: Priority-Maybe
• Removed labels: Priority-Low

[GoogleCodeExporter]

Decided to discard the gzip filenames. There are other archives out there that 
break 
completely because some particularly bright compressor called a .tar files 
"24342".

Original comment by paracel...@gmail.com on 13 Nov 2009 at 2:04

• Changed state: Fixed