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.
1. Add a property using popup under Extensibility Elements on WSDL view. 2. Open properties dlg. There are non-localized messages on it. See attached pics.
Created attachment 38988 [details] properties dlg
Created attachment 38989 [details] properties dlg todo
See also images for Bindings on the same tree view. Also I'd like to notice some properties without pseudo (marked in red).
Created attachment 38990 [details] output
Created attachment 38991 [details] soap binding
Created attachment 38992 [details] soap body
Created attachment 38993 [details] soap operation
Created attachment 38994 [details] soap addr
It isn't bpel project issue. I've looked at this issue and saw that nonlocalized text comes from *.xsd files. If it's appropriate then these files should be added into the l10n.list.entpack(localization list) file.
We have translators localize only Bundle.properties files (or html files for template descriptors or on line help) There has been problems before with doing xml based files since syntax is complex and translators are not technical or engineers and one small problem with syntax and it will not work/parse as needed. Please implement process to have these msgs/labels put into Bundle.properties and be able to be read from localized ones. ken.frank@sun.com
The issue was filed at wrong priority by mistake and now moving to the correct one.
The same problem with BindingPort tooltips. See attached pic
Created attachment 42198 [details] tooltip
is the funcitonality described here still part of nb6 product ? just checking since this was filed a long time ago. ken.frank@sun.com
This is not yet part of 6.0, and currently looking at how it can be done.
The plan to fix this bug is as follows: 1. Move schema documentation to bundle.properties using a unique key (which is LBL_$type_$name). 2. Put the unique key replacing the schema documentation in the schema. for attributes, the type is ATTRIBUTE for elements, the type is ELEMENT for complex types, the type is COMPLEX_TYPE for simple types, the type is SIMPLE_TYPE and name is the name of the element. So the documentation finder visitor will go through the schema documentation and get the key, and use that to query the bundle to get the message. This will solve I18N team problem that the messages should be in a bundle file.
Documentation is moved to bundle.properties as clarified in the dependent issues. property names are not be localized, unless as a grouped property.
reproducible: build 1010, XP.ja_JP Bindings: jms, soap, http, file, Extensibility Elements: property The issue is about their description in property dialog.
I'll check with the next build
verified: build 1014