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 96214

Summary: I18N localization of element/attribute name and documentation of binding nodes in property sheet
Product: xml Reporter: Ritesh Adval <radval>
Component: WSDL ToolsAssignee: Ritesh Adval <radval>
Status: RESOLVED INVALID    
Severity: blocker CC: kfrank
Priority: P3 Keywords: I18N
Version: 5.x   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:
Bug Depends on:    
Bug Blocks: 81362, 96641    

Description Ritesh Adval 2007-02-21 19:42:49 UTC
when showing the documentation for binding extensions attributes,
we should read the localized value.

The documentation tag can have a xml:lang attribute identifying the locale
specific content.

We should read the appropriate documentation which has a xml:lang attribute
matching the current locale of the platform where application is running.
Comment 1 Ritesh Adval 2007-02-28 00:58:01 UTC
The approach we follow for documentation localization in binding schema is as
follows.

There will be an spi to register optional bundle for looking at localized value
of element/attribute name and documentation.
 
Following is the key convention:

<element base name>=ancestor element name chain separated by underscore

element name key=<element base name>_displayName
element documentation key=<element base name>_documentation

attribute name key=<element base name>_<attribute name>_displayName
attribute documentation key=<element base name>_<attribute name>_documentation

if bundle is not provided then default element/attribute name will be whatever
name of element/attribute in schema. Similarly documentation will be whatever
documentation of element/attribute in schema.

Comment 2 Ritesh Adval 2007-03-06 00:48:07 UTC
We need to localize only the documentation coming from schema.
The element /attribute are binding language spec meta data and we should not be
localizing that.

I am closing this bug and open a new one just for documentation.