Details
-
Type: Task
-
Status: Closed
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.11.0
-
Component/s: Dev and Dep, i18n
-
Labels:
-
Epic Link:
Description
A new phase in the jalview build process is needed to verify that there are no invalid GUI message keys in the Jalview source code. Ideally, something like:
ant check-i18n
should search the code and check for all cases where an i18n bundle lookup occurs (ie where jalview.util.MessageManager.getString() is called), and report any cases where a key is not found in the message bundle.
ant check-i18n
should search the code and check for all cases where an i18n bundle lookup occurs (ie where jalview.util.MessageManager.getString() is called), and report any cases where a key is not found in the message bundle.
Attachments
Issue Links
- blocks
-
JAL-1355 Basic i18n support for bare strings shown in GUI
- In Progress