This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | I18N - Can not Display japanese file name on Manifest tab | ||
---|---|---|---|
Product: | obsolete | Reporter: | Ken Frank <kfrank> |
Component: | jarpackager | Assignee: | issues@obsolete <issues> |
Status: | CLOSED WONTFIX | ||
Severity: | blocker | CC: | jf4jbug |
Priority: | P2 | Keywords: | I18N |
Version: | -FFJ- | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Ken Frank
2001-07-23 21:08:47 UTC
*** Issue 13287 has been marked as a duplicate of this issue. *** This is a consequence of JDK bug 4260472, entered by Jesse Glick in August of 1999! I encourage anyone who cares about this to go to http://developer.java.sun.com/developer/bugParade/bugs/4260472.html and vote for this bug to be fixed. The jar packager never writes directly to the Manifest pane display. Instead, it adds attributes to the Manifest object (classes Manifest and Attributes in package java.util.jar), and lets the Manifest object format the output. Unfortunately, this class (along with the Atributes class) cannot handle doublebyte characters. In fact, it simply chops off the top byte, leading to the garbage described above. Note that there is no good way to work around this JDK bug. If the jar packager wrote directly to the display, the doublebyte characters would still be corrupted when the Manifest was serialized to the .jarContents file. Even supposing the doublebyte characters could be written correctly to the jar file, the running java application, using the Manifest object to read the jar's manifest, would see them as garbage (each byte of a doublebyte character would become part of a separate Java character.) This needs to be fixed in the JDK, ideally by treating a manifest as UTF-8. Not fixed, but addressed. Until the JDK resolves this issue, the IDE will not allow double-byte characters from being inserted into manifests, either by typing them in or by loading a file which contains them. *** Issue 33857 has been marked as a duplicate of this issue. *** Resolved for 3.3.x or earlier, no new info since then -> closing. Resolved for 3.4 or earlier, no new info since then -> closing. Resolved for 3.4 or earlier, no new info since then -> closing. |