This bug was originally found in developers' comments for 4651460.
 (JDC bug database)
--------------------------------------------------------------
  java.util.zip and winzip32.exe can NOT operate zip-files including 
  Japanese Path well. so-called garbled characters!! (UTF-8 vs MS932)
  Please resolve this too!!
-----
  This is a kind of internationalization bug, too.
  Because most ZIP application encode/decode file entries in platform's 
  native encoding, Java ZIP application isn't compatible with them.
  I recommend to add a charset parameter to ZIP-related methods.
-----
  And the bug is still in the newest JDK1.4. 
  We hope this problem can be resolved sooner.
--------------------------------------------------------------

Java2's java.util.zip cannot get files properly from a zipfile which is
made with Winzip which is commonly-used zip/unzip software when Japanese
name is included in the zipfile.
This is very inconvenient for Japanese developers and users.
Posted Date : 2005-08-03 08:40:29.0

N/A

Yes, this should be fixed, not just for Japanese but for all non-ASCII
charsets.

--   xxxxx@xxxxx   2002/12/16


I believe this is a duplicate of 4244499.
  xxxxx@xxxxx   2005-1-29 00:24:19 GMT
We plan to address this and other issues related to character encodings in zip/jar files in the dolphin release.
Posted Date : 2005-12-06 16:38:04.0

With newly added constructors in zip/in/out/file classes we can created winzip "compatible" zip file with non-ascii names/comments
Posted Date : 2009-04-16 22:25:48.0

YES AFTER CREATING AN APP THAT USES ZIP API'S
I'VE FOUND THAT I CAN'T USE IT 
I THINK IT'S A MAJOR BLOW TO THE JAVA INI18 STATMENT

have a look at http://groboutils.sourceforge.net/docs/projects/5/api/net/sourceforge/groboutils/codecoverage/v2/ant/zip/ZipFile.html

perhaps this helps

Hi,

this is a duplicate of acknowledged real bugs 4244499 and 4688771 , at the moment of writing both within the bugs top25.

For the first one being the original and leading in top25, I would suggest to move the votes to it. This one could be closed as duplicated.

And yes, this should be fixed, but now for almost six years... :-(