Community
Participate
Working Groups
Build ID: I20070625-1500 Steps To Reproduce: I think it would be VERY useful if Eclipse JDT provided an own resource bundle editor, like NetBeans does. I think a good starting point could be the Resource Bundle Editor: http://www.resourcebundleeditor.com/ It's open source and maybe it could be included in the official JDT project? Some features it would be nice to have: - hierarchical view of keys using dots (".") in their names - text-area editor for each key value - additional table view of key values (like NetBeans) - support for the difference between empty values and null (missing) values, respecting the java.util.ResourceBundle key search mechanism - transparent handling of each locale property file, with automatic conversion to escaped ISO-8859-1 charset encoding All these features are already in Resource Bundle Editor, except for the second one (which is in JInto, for example). There are also some problems with the handling of empty values vs null values. The main problem of this third-party plugin is that it is not updated very frequently and now it has some small issues with Eclipse 3.3. More information:
I'm marking this as wontfix, as we already have the properties file editor and along that line feature enhancements for that editor (e.g. show outline), provide wysiwyg feature etc. (look for [nls tooling] in the summary). There are no plans to provide an additional editor.
Hi Daniel, the fact that resource bundles usually work with .properties file does not simply mean that the properties file editor is really useful when working with resource bundles: it is like saying that an advanced Java text editor like JEdit is the same as Eclipse because it allows to edit Java files... Providing the outline for a property file is certainly useful, but how to jump to one locale property file to another? How to easily translate new strings for one or more locale? How to quickly compare two locale properties files? If you ever used ResourceBundleEditor or NetBeans's editor, you should understand what I mean. I made a search for "[nls tooling]", but I couldn't find any answer to these questions. I know Eclipse can "externalize strings", yes... but then? How should a developer manage those localization properties files? Using the properties file editor on each single .properties file, manually adding/removing/renaming keys on each file and continuously jumping from one file to another? It's a nightmare! And it's an error-prone process. Something similar is outlined in bug #113080, but I think this is just part of the problem. I'm sorry to see that, even if there is currently no plan for a new editor, my proposal isn't even taken into consideration... Mauro.
>I'm sorry to see that, even if there is currently no plan for a new editor, my >proposal isn't even taken into consideration... It's just not on our plan. If someone really wants this feature they can implement it and contribute it - that's what open source is all about.
I recently heard that Resource Bundle Editor will become part of Eclipse Babel project. I don't know if my enhancement request contributed in any way for this to happen, however I'm very happy and I hope that this will help Eclipse to improve on this aspect, too. Mauro.
See also bug 239475
