[Bug 580961] Re: unzip fails to deal correctly with filename encodings

[Lanoxx]

>test case:
>do an "unzip -l" on the file http://tinyurl.com/2aofpxs and witness the question marks

Sorry for posting on this already quite long bug. I am using Ubuntu
14.04 (LTS) with all the latest updates.

This bug is still present for me. I need to explicitly pass `-O 850` to
enable codepage 850 in order to resolve it. Interestingly passing CP-850
does not work. Took me quite some time to figure this out.

Not the subtle differences in the resulting filename for the two
commands below:

ERROR:

  $unzip Gyakorlat\ hallgatói\ segédlet\ -\ 7.\ Webes\ alkalmazások\ fejlesztése.zip 
Archive:  Gyakorlat hallgatói segédlet - 7. Webes alkalmazások fejlesztése.zip
  inflating: Gyakorlat hallgatвi segВdlet - 7. Webes alkalmazаsok fejlesztВse.doc  

WORKAROUND:

 $unzip -O 850 Gyakorlat\ hallgatói\ segédlet\ -\ 7.\ Webes\ alkalmazások\ fejlesztése.zip 
Archive:  Gyakorlat hallgatói segédlet - 7. Webes alkalmazások fejlesztése.zip
  inflating: Gyakorlat hallgatói segédlet - 7. Webes alkalmazások fejlesztése.doc  

Question: Is this a regression or am I experiencing a different bug
unrelated to this one? If I am not mistaken then this was fixed before
Ubuntu 14.04 and so the fix should also be included in Ubuntu 14.04 or
not?

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to unzip in Ubuntu.
https://bugs.launchpad.net/bugs/580961

Title:
  unzip fails to deal correctly with filename encodings

Status in File Roller:
  Confirmed
Status in Linux Mint:
  Triaged
Status in Ubuntu Japanese Kaizen Project:
  Fix Committed
Status in unzip:
  Unknown
Status in unzip package in Ubuntu:
  Fix Released
Status in unzip source package in Precise:
  Fix Released
Status in unzip source package in Quantal:
  Fix Released
Status in unzip source package in Raring:
  Fix Released
Status in unzip package in Debian:
  Confirmed
Status in Gentoo Linux:
  Won't Fix
Status in unzip package in Mandriva:
  Unknown
Status in unzip package in openSUSE:
  Fix Released

Bug description:
  Binary package hint: unzip

  This is a fairly annoying bug that's been around and known at least
  since 2005.  It's very visible as it will very often make exchange of
  zip files with Windows users impossible, for example.  As such, it
  gathered it's fair share of "me too" and "how dare you haven't fixed
  this yet!!111!" comments.

  Problem description:
  zip/unzip and the specification fall short when dealing with non-ASCII filenames not encoded in UTF-8

  test case:
  do an "unzip -l" on the file http://tinyurl.com/2aofpxs and witness the question marks

  affected programs:
  the problem is in unzip itself, but affects GUI like xarchiver, file-roller, etc. that rely on unzip for the decompression

  suggested solutions (most are workarounds, not proper fixes):
   a) reintroduce patch for codepage-based zip filenames: bug 477755, http://tinyurl.com/2aqdbqg (Ubuntu blueprint)
   b) unzip filename according to locale: bug 203609
   c) Ubuntu JP has a patch, probably not generally applicable, bug 269482
   d) Russian altlinux distro uses natspec lib and patched zip binary

  natspec was mentioned in bug 477755 comment #2 and may indeed be a
  proper fix, needs closer inspection (I haven't really looked, yet.  As
  discussed in https://bugzilla.gnome.org/show_bug.cgi?id=306403 there
  is no failsafe, straight-forward way to fix this in all cases.
  Nonetheless, the current situation can and should be improved.
  There's some good ideas floating around.  It needs somebody to pull
  and wrap them together.

  It's unfortunate the FOSS community so far hasn't been able to fix
  this rather visible problem.  I'm opening this ticket as a master bug
  and clean slate to document the issue and current status.  Please
  don't ruin it by making above-mentioned unhelpful comments, they
  actually slow things down!  Please don't nominate for a release.

  Unless you're a dev and can provide a patch, you should think VERY
  carefully to do anything but

  1) subscribe yourself to this ticket
  2) mark this bug as affecting you
  3) tell me via mail about other bugs you think are a duplicate of this one, discussing the same problem

  1) to 3) will showcase to the devs how many people are affected and
  that is the only real chance we have for somebody to take a serious
  look.  "Me too" comments do the opposite, so again, please don't do
  it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions