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.
Steps: 1. launch multilanguage version of NetBeans 3.6 on Solaris x86 with Chinese locale. 2. Create .java program whose main class name is in Chinese, or whose package name is in Chinese. * Make sure the program can be compiled and executed correctly. 3. Create JAR Recipe; and add the .java created in step 2 to it. 4. Add Main-Class to the manifest file and generate. Result: 1. In step 4, after press Generate button, the Main-Class entry containing Chinese characters disappears right away. 2. If choose OK and execute the JAR Recipe, an error will appear: "Fail to load Main-Class manifest attribute from ...".
It seem reproducable in C locale and workaround is to create a local manifest file and the load this file from ....
But manifest file containing double-byte characters can't be manually loaded either. If convert to ascii, the compiler doesn't read the class name.
is this still an issue with nb4.0 since I dont think jar receipe/packager is present anymore. please add word I18N to front of synopsis of any i18n bugs, besides putting it as keyword. ken.frank@sun.com 06/08/2004
need to check the spec but I think manifest format does not allow you to put chinese chars there Jesse, do you know?
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4260472 Although the JAR manifest spec implies that UTF-8 should be used as the character encoding, it is not explicitly stated, and in fact the JRE's current impl does not handle international characters as far as I know. So for now, sorry - you must name your main class and its package in ASCII.
closed
just checking to see if this is still true for jdk6, that ascii must be used and thus non ascii will still be seen correctly in ide in manifest file or info from manifest file. ken.frank@sun.com
Well, in a NB dev build running on JDK 7 on a Linux laptop using UTF-8 system encoding I created a new project w/ main class, called "Hezky Česky". Running via F6 was fine. I built the JAR with F11. The resulting JAR's manifest has Main-Class: hezkyčesky.Main in UTF-8 format. java -jar on the command line runs it just fine. NB by default creates Hezky__esky.jar to be on the safe side (it will choose conservative JAR names), though if you care you can edit project.properties: dist.jar=${dist.dir}/Hezky_\u010Cesky.jar and the resulting Hezky_Česky.jar will also work fine. (Note that non-ISO-8859-1 chars are not permitted raw in .properties files; the Insert Unicode module from AU is helpful here, or you can use the property sheet.) So as usual, the summary is: if you are using Linux with UTF-8 encoding, you have nothing to worry about; if you are using another OS, or Linux with a legacy encoding, you can try and maybe it will work.