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 211528 - Branding does not permit i18n localization
Summary: Branding does not permit i18n localization
Status: RESOLVED WONTFIX
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.1.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-20 17:37 UTC by fabien_nisol
Modified: 2012-04-25 15:57 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description fabien_nisol 2012-04-20 17:37:27 UTC
When using the branding tool, in the Resource Bundles tab, one cannot modify the resource bundle value for a particular language

To reproduce: 

right click on project -> branding
go to Resource Bundles tab
take a particular resource bundle/value 
   (eg org/apache/tools/ant/module/Bundle.propertise/Always_show_output = Always Show &Output)
right click "Add to branding"


the dialog should permit to modify the branding for a different language (in the way the "New locale" dialog works)

I also tried to add the bundle file manualy, but the particular bundle file does not seem to be loaded into the application
Comment 1 Jesse Glick 2012-04-25 02:06:01 UTC
The Branding dialog is only for managing branding, not localization. Currently there is no GUI feature for assisting with localization of a Platform app; you need to do it manually.
Comment 2 fabien_nisol 2012-04-25 02:49:26 UTC
I understand what you mean, and manual procedure would work pretty well, but, as I said at the end of my issue report:

"I also tried to add the bundle file manualy, but the particular bundle file
does not seem to be loaded into the application"

which means that manually creating the localized branding bundle file does not work...

Moreover, the manual approach is fine, but it is kind of cumbersome

1. You have to replace the original default branding in order to create the wanted localized branding
2. You have to find the file that was just created manually, in the "File explorer" , those files are not shown in the project "Important files"
3. Once your particular branding value is localized, you have to "delete" the default branding you just created.

All this makes me think the branding window should permit to specify the branding locale we want to modify, to make the process faster

I understand it is some kind of unwanted feature duplication, so I admit we can live with "manual" procedure, but at least, can we make it work as expected ?
Comment 3 Jesse Glick 2012-04-25 15:57:33 UTC
(In reply to comment #2)
> "I also tried to add the bundle file manualy, but the particular bundle file
> does not seem to be loaded into the application"
> 
> which means that manually creating the localized branding bundle file does not
> work...

Sure it does, if you do it right; presumably you did it wrong. I do not know what exactly you tried but this is a matter for mailing lists, FAQs, etc. (*) unless you have read the Module System API's specification of branding and localization and can demonstrate a specific bug in the Platform or its tooling.

> the manual approach is fine, but it is kind of cumbersome

Yes, we know. But we have no resources to develop tooling for this.

(*) For example: http://wiki.netbeans.org/DevFaqMavenL10N