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.

Bug 96813 - I18N - there are nodes in wsdl tree without localized description
Summary: I18N - there are nodes in wsdl tree without localized description
Status: VERIFIED FIXED
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords: I18N
Depends on: 96734 118483
Blocks:
  Show dependency tree
 
Reported: 2007-02-28 19:05 UTC by kaa
Modified: 2007-10-15 19:01 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
properties dlg (52.74 KB, application/octet-stream)
2007-02-28 19:08 UTC, kaa
Details
properties dlg todo (45.21 KB, application/octet-stream)
2007-02-28 19:09 UTC, kaa
Details
output (70.97 KB, application/octet-stream)
2007-02-28 19:17 UTC, kaa
Details
soap binding (56.08 KB, application/octet-stream)
2007-02-28 19:18 UTC, kaa
Details
soap body (86.49 KB, application/octet-stream)
2007-02-28 19:18 UTC, kaa
Details
soap operation (87.09 KB, application/octet-stream)
2007-02-28 19:19 UTC, kaa
Details
soap addr (105.01 KB, application/octet-stream)
2007-02-28 19:20 UTC, kaa
Details
tooltip (53.01 KB, application/octet-stream)
2007-05-07 16:38 UTC, kaa
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kaa 2007-02-28 19:05:30 UTC
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.
Comment 1 kaa 2007-02-28 19:08:26 UTC
Created attachment 38988 [details]
properties dlg
Comment 2 kaa 2007-02-28 19:09:13 UTC
Created attachment 38989 [details]
properties dlg todo
Comment 3 kaa 2007-02-28 19:14:20 UTC
See also images for Bindings on the same tree view.
Also I'd like to notice some properties without pseudo (marked in red). 
Comment 4 kaa 2007-02-28 19:17:11 UTC
Created attachment 38990 [details]
output
Comment 5 kaa 2007-02-28 19:18:03 UTC
Created attachment 38991 [details]
soap binding
Comment 6 kaa 2007-02-28 19:18:43 UTC
Created attachment 38992 [details]
soap body
Comment 7 kaa 2007-02-28 19:19:19 UTC
Created attachment 38993 [details]
soap operation
Comment 8 kaa 2007-02-28 19:20:03 UTC
Created attachment 38994 [details]
soap addr
Comment 9 Vitaly Bychkov 2007-03-05 11:52:41 UTC
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.
Comment 10 Ken Frank 2007-03-05 15:37:31 UTC
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
Comment 11 kaa 2007-03-09 18:25:10 UTC
The issue was filed at wrong priority by mistake and now moving to the correct one.
Comment 12 kaa 2007-05-07 16:37:14 UTC
The same problem with BindingPort tooltips.
See attached pic
Comment 13 kaa 2007-05-07 16:38:18 UTC
Created attachment 42198 [details]
tooltip
Comment 14 Ken Frank 2007-10-03 17:29:45 UTC
is the funcitonality described here still part of nb6 product ?

just checking since this was filed a long time ago.

ken.frank@sun.com
Comment 15 Shivanand Kini 2007-10-03 18:42:58 UTC
This is not yet part of 6.0, and currently looking at how it can be done.
Comment 16 Shivanand Kini 2007-10-10 01:17:11 UTC
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.
Comment 17 Shivanand Kini 2007-10-12 02:24:18 UTC
Documentation is moved to bundle.properties as clarified in the dependent issues.
property names are not be localized, unless as a grouped property.
Comment 18 kaa 2007-10-15 16:46:17 UTC
reproducible: build 1010, XP.ja_JP
Bindings: jms, soap, http, file,
Extensibility Elements: property
The issue is about their description in property dialog.
Comment 19 kaa 2007-10-15 18:56:10 UTC
I'll check with the next build
Comment 20 kaa 2007-10-15 19:01:06 UTC
verified: build 1014