Bug #2270
openTRACKING: Localization and Improvement of User-Visible Messaging Strings
0%
Description
There are several bugs that pertain to changing the various messaging strings
that the user sees (general UI text, labels etc) or may potentially see (error
messages etc). Relevant bugs have been marked as dependencies of this bug, for
tracking purposes
As an approach to this tasks, I suggest looking at using Java's inbuilt
localization functionality, which offers the following benefits:
1) standard and well-tested framework already in place as part of the JDK - no
need to create our own solution
2) Gathers all these strings in one place, so text changes can be addressed
easily now and in future
3) Gives us the benefit of being able to internationalize the app easily at a
later date, when demand escalates in non-English-speaking countries...
Related issues
Updated by Matthew Brooke almost 19 years ago
Have started using ResourceBundles (text files in
configs/ptolemy/configs/kepler/ all named "ui*_en_US.properties"), for top-level
menu text ("uiMenuMappings_en_US.properties"), context menu text
("uiContextMenuMappings_en_US.properties"), and dialog text
("uiDisplayText_en_US.properties").
Updated by Matthew Brooke over 18 years ago
- NOTE that there is one ResourceBundle specifically for display text (ie text that appears in the UI, that the user sees) - it is cunningly named:
configs/ptolemy/configs/kepler/uiDisplayText_en_US.properties"
Use it or be damned!