Community
Participate
Working Groups
While Eclipse is quite versatile when it comes to supported languages for the general platform (see article "Teach Your Eclipse to Speak the Local Lingo") the Java Tools do not support i18n issues that well so far. Both features of the NetBeans platform (where PropertyResourceBundles are recognised and the addition of a new locale/language creates all the required files automatically) and Unicode-capable plugins ALREADY existing for Ecliple would be a vital enhancement for the platform and i18n support to developers. The Eclipse Plugin is the "PropertiesEditor" available at Sourceforge.jp
Here's the URL of the SF.jp project
(In reply to comment #1) > Here's the URL of the SF.jp project http://sourceforge.jp/projects/propedit
Move to JDT/UI.
Could you explain in this bug in more detail what you miss (please use latest 3.2 M5 or upcoming M6 as a reference) in Eclipse and what the most wanted items are? Thanks. Please reopen after providing above information.
Sure. I'll try to add some screenshots and might also describe the benefits from those tools for UI developers and translators...
(In reply to comment #5) > Sure. > I'll try to add some screenshots and might also describe the benefits from > those tools for UI developers and translators...
Created attachment 37777 [details] PropertiesEditor in Edit Mode Supporting Unicode Characters to be entered directly
Created attachment 37778 [details] Properties Editor in Preview Mode This is the preview of the actual properties file, not the way the character is rendered on the screen (maybe the 2 terms could be different?)
Created attachment 37779 [details] Properties Editor View in NetBeans NetBeans automatically detects the language and country for a Locale extension. It also provides a wizard to add new locales creating and naming the file copy correctly.
Comment 7 is covered by bug 65571 and along with this a way to watch both - the file as it is on disc and with native characters makes sense (I added a comment to bug 65571). Comment 9 describes improved support for managing a properties files for different languages. This is bug 113080. Marking this one as duplicate. *** This bug has been marked as a duplicate of 113080 ***
IC. Looks like i18n is not too high on the Agenda despite Mike's statements praising some IBM Localisation Toolkit and its possible influence on Eclipse ?;-) bug 113080 is marked "Resolved", too. Does this mean it will NEVER be dealt with, or could it be reopened when there is "Time" ?;-) The better Unicode Support seems higher on the agenda, and if the best functionality of the PropertiesEditor might at some point become Eclipse Core this would at least be half done and better than nothing...
>bug 113080 is marked "Resolved", too. Does this mean it will NEVER be dealt >with, or could it be reopened when there is "Time" ?;-) It doesn't mean 'never', otherwise we would have closed it as WONTFIX. It will be reopened either if it gets higher priority than other items or if someone volunteers to do work on this.
