Comment 5 for bug 683668

Hello Robert,
Thank you for digging into it.
From your wording suggestions I think "'file' command gives wrong type for
data being compressed with 'compress'" describes it best.
Indeed I was trying to process a bunch of files which had been compressed
with 'compress' on HP-UX.
Because I had a large list of those files without the .Z extension I needed
to check which where compressed and which not.
Thus I used something like:
   file $Filename | grep -q "compressed" && { cat $Filename | uncompress ; }
|| cat $Filename

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
Robert Roth
Sent: Donnerstag, 2. Dezember 2010 23:40
To: <email address hidden>
Subject: [Bug 683668] Re: file command in 10.10 produces wrong message

My fix is not the best one. This bug needs a better wording. Archives are
described by the file utility as "gzip compressed data", "7-zip compressed
data", etc. "compress'd data" stands for an abbreviation of the ugly wording
"compress compressed data" (compress being the name of the app used to
compress) or "compressed data compressed with compress"
:) It could be "LZW compressed data" or "data compressed usin compress".
Please suggest a correct wording having the same meaning as the above, and
I'll do the patch.

** Tags added: patch

--
You received this bug notification because you are a direct subscriber of
the bug.
https://bugs.launchpad.net/bugs/683668

Title:
  file command in 10.10 produces wrong message

Status in "file" package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: file

in 10.10 the file command for a compressed (gzip) file says:
 ... compress'd...
The apostroph in here is completely wrong to me.
It messed up things in my output parser and it should say compressed
instead of compress'd as in previous versions of ubuntu.

To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/683668/+subscribe