JDK-4700978 : ZipFile can't treat Japanese name in a zipfile properly
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.util.jar
  • Affected Version: 1.3.1_15,1.4.0
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_nt,windows_2003
  • CPU: x86
  • Submitted: 2002-06-12
  • Updated: 2009-04-25
  • Resolved: 2009-04-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
7 b57Fixed
Related Reports
Relates :  
Relates :  
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.

EVALUATION With newly added constructors in zip/in/out/file classes we can created winzip "compatible" zip file with non-ascii names/comments

EVALUATION We plan to address this and other issues related to character encodings in zip/jar files in the dolphin release.

EVALUATION Yes, this should be fixed, not just for Japanese but for all non-ASCII charsets. -- ###@###.### 2002/12/16 I believe this is a duplicate of 4244499. ###@###.### 2005-1-29 00:24:19 GMT