1. this is NOT about using non ascii in mobility project names - that is a known restriction.
this is NOT related to using a translated nb.
2. this happens at least in asian locales on linux, not sure about other non en ones.
3. reported as not happening using jdk5.
4. . this might be related to some jdk issues not fixed in jdk6 but it might not be - please
don't close as a jdk issue until sure its not nb; see comment 6 and 8. for more on this.
a. be in ja locale on linux (was using RH4)
b. create mobility project or demo project.
c. run it
d. emulator does not appear.
e. I did not see exceptions.
f. run nb in en locale - same steps - emulator appears.
6. I installed wtk myself and ran in ja locale, using ktoolbar, and was able to run
the demo apps
a. I then ran the netbeans created app or demo (in <projectdir>/dist, using the wtk own emulator
(modified wtk own run.sh to point to correct path of wtk emulator) - and in ja
locale was able to run the netbeans created app, ie <projectdir>/dist/UIDemo.jar
b. this seems to mean that it might be problem in nb rather than in jdk
7. regardless of cause, we need to get relnote and faq for nb6 fcs that tells about a workaround,
and gives steps in context of the wtk installed with nb, not about a standalone one.
(whether the w.o described in 6 or something else, like some config in some mobility project
props or the wtk itself from tools->java platforms or some other one)
8. the jdk issues mentioned that might be related are
it seems to be ok when running in ja utf-8 locale on linux, regardless if the
project encoding property is utf-8 or euc-jp.
But in regular ja locale (euc-jp) encoding, using utf-8 or euc-jp project encoding does
I think the problem does happen when am in ja utf8 locale, unlike what I had commented
can team provide an initial evaluation ?
Please don't forget to add jf4jbug at filing I18N issue.
wtk issue 663631 was filed about this.
correct bugster bug number is 6636361
jdk6 u10 build 12 is recently out with the fix for this issue ported to it.
I did a quick test on rh4 in ja locale using this jdk, and it seems to be fixed
both in using netbeans itself and using wtk emulator standalone using ktoolbar.
lets wait a bit to close it for some more testing.
jdk6u10 won't officially be out until August, so we can keep release
notes item on this for 6.1.
Since we can do nothing about it I would rather close this issue and add necessary information to the 6.1 release note.
Luskas could you test it with jdk6 u10 build 12? Thanks.
The JDK6 issue #6389282 is already in the release notes for 6.0 Mobility. I will add a note mentioning the fixed jdk6
u10 build 12. Should I reference and link to a different bug database issue for the release note entry? If yes, which
one does QA recommend? :)
as to the bug database to use, I dont know if all sun bug databases
are visible to external users; also don't know if the jdk updates
not yet released externally are available to external users.
Closing as WONTFIX.
Nothing can be done on mobility side. Please, update your JDK to the version with the fix to be able to run in Asian
Brad, keep it in the RN for now.