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.
In project settings->workspaces-> editor (or other workspaces), the value of Toolbar Configuration, Standard or Debugging, does not come from locale specific message files, even though these labels are present in those files The names of all the workspace areas and the names of all windows on the windows->windows menu does come from message files, so I don think this is related to other issues of not seeing certain labels if FFJ not installed in locale it is run in.
Why are now names of toolbars configurations labeled //NOI18N? Assigning.
Assign to Radko. It should be easy.
There is no support to localize toolbar configurations. The configurations are stored in the XML files and the name of the file is the name of the configuration which is shown in the toolbar configuration property editor. Possible fix: add a tag to the configuration file which will describe how to get the localized name (e.g. from which bundle to get the localized name).
Target milestone -> 3.3.1.
I'm changing target milestone to 3.4, as this includes API change (DTD format of xml which describes toolbar settings in in fact kind of public API)
Evaluation: Add support for toolbar localization, more work.
Is this one related to 19966 about toolbars, which is fixed ? Or is this still an issue, since api changes mentioned or other fixes might have happened in last few months ? ken.frank@sun.com 04/19/2002
AFAIK, unfortunately this is still an issue. Whole toolbar configuration impl is "not so good" (to be polite) when it comes to localization and branding. Although bug seems to be easy to fix, significant architecture redesign and rewrite is needed :-(
Assigning to Dafe
uff, too late for 3.4, I'm sorry. Changing milestone. Raising priority to emphasize importance.
added ARCH and API keywords to indicate that changes in those areas are needed. In fact the whole toolbar code should be rewritten. It's too buggy.
Yarda: In my opinion there is a solution. If there is a definition: <file name="Standard.xml" url="resources/Standard.xml" /> in the module layer. The localization JAR can add file "resources/Standard_ja.xml" and this file will be used instead of the "Standard.xml" if started with Japanese locale. (the magic should be done by the nbresloc protocol, that is the default one for url="nbresloc:resouces/Standard.xml").
Can solution be to not require an xml file to be localized ? In netbeans and ffj, 99% of time the use of localized bundle files is all that is needed. The xml file in module's main jar and other module code take care of the logic to use ja bundle file when user in ja locale. Labels like these should be just in bundle files, as per netbeans i18n guidelines. ken.frank@sun.com 07/08/2002
I'm working on it...
Ken, some details for you: - Yes, part of solution is not to localize xml file in question. In fact, xml isn't localized now and it will stay this way. Yarda's comment expected that we need to localize info inside xml file (which is not needed here) - right solution (again thanks Yarda) is to localize name of xml file (through standard bundle way) and update code on various places to work with localized names of toolbar configurations correctly.
fixed in main trunk. localization now works through standard file object localization in bundles. I've added english localization to the org.netbeans.core.Bundle.properties: Toolbars/Standard.xml=Standard Toolbars/Debugging.xml=Debugging To get correct japanese translation, it's needed to modify org.netbeans.core.Bundle_ja.properties as usual. Thx.
verified in [nb_dev](20021016)