Community
Participate
Working Groups
This applies to the standard java string externalisation (not the eclipse way). The "Externalise Strings" Wizard is good, if you just want to externalise the strings of a plain new project. But what about existings projects ? I have already localized my app, but now i have to add additional features (and additional strings). No problem for the default locale, but what about the properties files for the other locales ? You have either to fiddle in the additional keys by hand or throw away the existing translated properties files to copy it from the standard locale (and do the full translation work once again). Please add an option to the dialog to select the locale. When selecting a new locale the wizard should add all missing keys to the corresponding locale file.
Sounds like support for translators to me. Not high priority currently...
Not really for translator but for developers. It is not the translator who has to add additional keys to the localised property files.
Not planned to add this for now.
*** Bug 134407 has been marked as a duplicate of this bug. ***
*** Bug 131588 has been marked as a duplicate of this bug. ***
*** Bug 140988 has been marked as a duplicate of this bug. ***
*** Bug 50978 has been marked as a duplicate of this bug. ***
Get rid of deprecated state.
*** Bug 213610 has been marked as a duplicate of this bug. ***