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.
In tools-options->object types, the listings IDL Objects, IOR Objects, RMI Sources do not come from Bundle files even though Bundle files may have those words. If these come from manifest files, which are not now localized, can they (and any other items that can be localized) be put into bundle files. There is a mechanism now in place to do this; see 12549.
RMIDataLoad contains: setDisplayName(NbBundle.getMessage (RMIDataLoader.class, "CTL_RMIDataLoader")); // NOI18N Bundle.properties contains: CTL_RMIDataLoader=RMI Sources there is no other way how to set "RMI Sources" name
verified
I still see IOR Objects and IDL Objects as not from locale specific message file. I have only started this FFJ in ja locale, never in C locale. I see some other modules like this, so could this be issue of not putting manifest info into bundle files, or some serialization issue ?
Yes, problem is with serialized data. If you restart IDE with different locale, you probably have to reinstall (disable/enable) module to recreate settings under new locale. When user first starts IDE with C or Ja locale, everything is OK (until he change the locale).
Do you see anything else than IOR and IDL not localized? IOR and IDL are from CORBA module.
The Words IOR Objects and IDL Objects are only in Bundle files. They must come from Bundle.
I have only started it in ja locale, not at all in C locale. Yes, there are other parts not showing properly, some from web apps, some ejb, one from database and bugs also were filed. Some have been fixed and some, like this one, said fixed but are not. k.frank 12.03.01
Followed suggestion of someone from another module with this issue - turned off a module, then on. I did this with corba module, and the 2 labels of IOR and IDL did appear from localized bundle file. But I think it still a bug as: 1. most other parts of object types labels do not have this problem 2. I was only in ja locale, not C 3. Users should not need to turn off and on modules like this. k. frank 12.03/01
This bug does not appear when user don't change locales. The only way to reproduce it is to start IDE first time with one locale and then with another locale and for both use the same userdir. User settings are localized and serialized, when you use new userdir or disable/enable module, they are regenerated with propper locale. Object type listings come from bundles, but not each start of IDE.
Fine, both IOR and IDL dat objects were rewritten to use defaultDisplayName instead of the setting it in initialize method (they are no more serialized). Ken, could you be so kind and test it, if it works. The bug was fixed both in main trunk and release33 branch.
It does not work. I think we have a disconnect here - I've been saying that I have not started ide in C locale, only ja locale. So the changing of locales does not appear to be an issue here. Could it be that the locale in which it is unzipped is important ? I didn't think anything happens during unzip of nb build. If not,then, as mentioned below, the enable/disable worked, but that is not solution I don't think. And also, why do I see most other object type labels coming from locale bundle files, if this is a problem in which locale one starts it in. Please reopen this if appropriate. k. frank 12.04.2001
Verified on Build 200112050331. My verification way was: - set locale to ja - Download NB - Run NB - Confirm the "RMI Sources" are English (Because this is English Version) - Localize rmi.jar and copy rmi_ja.jar into modules/locale - Run NB - Confirm the "RMI Sources" is still English (Because my userdir still has previous product information) - Remove my user dir "~/nbuser" - Run NB - Confirm the "RMI Sources" is Japanese As for IDL Objects, and IOR Objects, almost steps are same. Because the user doesn't localize like me, and because almost user use same locale when both downloading and executing, it seems that we don't have any problems. All users see the localized messages without any special operations. Ken, would you please try the steps which I've done? I believe you see the localized messages.
Consistent use of the I18N keyword.
Resolved for 3.4.x or earlier, no new info since then -> closing.