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.
Summary: | Rename main "GoTo" menu to "Navigate" | ||
---|---|---|---|
Product: | editor | Reporter: | jrojcek <jrojcek> |
Component: | -- Other -- | Assignee: | Jan Lahoda <jlahoda> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | CC: | jrojcek, phrebejk |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 104411 | ||
Attachments: | "GoTo" label is shown instead of "Navigate" in main menu |
Description
jrojcek
2007-04-13 15:54:04 UTC
There is no GoTo in main menu. Maybe tou are talking about the popup menu in editor. In this case please reopen and specify what should be renamed. You're right. It's not there. It was probably something weird with the build or my vision. "GoTo" is there again. ;-) I downloaded the all-in-one zip from: http://bits.nbextras.org/netbeans/6.0/nightly/latest/zip/ And started up the IDE with clean userdir. The "GoTo" menu was there instead of "Navigate". I'll attach screenshot. About info: NetBeans IDE Dev (Build 070420) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 en_US (nb); Cp1252 Created attachment 41346 [details]
"GoTo" label is shown instead of "Navigate" in main menu
Problem is that some modules are providing incorrect localization for Menu/GoTo. I fixed this problem in java/source in issue #101220. It seems that there was another occurrence of the bad localization in scripting/ruby. I will search whole big IDE for the incorrect pattern on Monday to ensure this does not reappear. Checking in layer.xml; /cvs/scripting/ruby/railsprojects/src/org/netbeans/modules/ruby/railsprojects/ui/resources/layer.xml,v <-- layer.xml new revision: 1.7; previous revision: 1.6 done I have checked out stable_nowww (and contrib+cnd) a checked all .xml files in this checkout. I haven't found any occurrence of the bad localization, so the problem hopefully should be fixed (for now). Please feel free to reopen if it happens again with a build that contains the fix from Friday. Thanks. |