Product Version: NetBeans IDE Dev (Build 200804210001)
Java: 1.6.0_05; Java HotSpot(TM) Client VM 10.0-b19
System: Windows XP version 5.1 running on x86; MS932; ja_JP (nb)
font size 16
1. Create EJB Module
2. Add New -> JavaObjects -> Customizer
3. DnD button from the palette
4. Select it and choose Bindings from Properties
5. Move cursor through the ist of bindings
All of them have tooltips and description not from pseudo localized bundle file.
I'm running in the Japan locale, using a pseudo localized Netbeans.
Created attachment 60565 [details]
since its about missing msg/tooltip and since
the patch fixes are translated, are marking
with the patch 2 status whiteboard words - might
this one be fixed for the patch 2 ?
These texts are not stored in NB bundle files, they are provided by components through property descriptors obtained
from BeanInfo or from binding infrastructure. See java.beans.PropertyDescriptor.getShortDescription() - this method
should return localized description (it is up to component vendors to implement it).
are these tooltips/description important enough to have be translatable
so that we might should have somewrapper module that can get and show that information
via bundle files ?
I think but not sure that this has been done in some cases, and am just
asking about it.
or perhaps its as you mention requirement that component providers
provide us with some translations ? are these providers a jdk or other
sun team ?
> are these tooltips/description important enough to have be translatable?
These descriptions correspond to the descriptions of get<Property> and set<Property> methods in the corresponding
JavaDoc. As we(=Sun) do not provide translated version of JavaDoc then I believe that it would be an overkill to do
our own translations in NetBeans.
> I think but not sure that this has been done in some cases, and am just asking about it.
No such attempt has been done in this area, so far.
> are these providers a jdk or other sun team ?
Depends on who is the provider of your components. It can be JDK (for standard Swing components), other sun team (for
example for SwingX components) or any 3rd party component vendor.