Description
The team which is localizing the 10.9 messages would like to audit our existing messages to ensure that they are easy to translate. A quick glance at their audit results shows many issues in the following categories:
1) Multi-line messages whose formatting confuses the translators. Translators tend to be language experts and not experts in the arcana of how Java properties files are formatted. I am hoping that these issues can be addressed by simply prefixing the multi-line messages with comments, explaining the arcane formatting.
2) Grammar, punctuation, and capitalization problems. I think we should just clean these up.
I am filing this issue as a place to hold patches which address issues raised by the localization audit.
Attachments
Attachments
Issue Links
- breaks
-
DERBY-5888 ServerPropertiesTest.testToggleLogConnections fails because of unexpected output
- Closed
- is related to
-
DERBY-5885 The order of argument names in messages.xml is sometimes wrong when the arguments occur in the message out of sequence.
- Closed
-
DERBY-5886 FILE_CANNOT_REMOVE_FILE exception prints garbage.
- Closed
-
DERBY-5887 Garbage printed for error LOG_UNDO_FAILED
- Closed
-
DERBY-5891 The French translations of a couple engine messages need to have their single-quotes escaped.
- Closed
-
DERBY-5884 Remove references to SQL-J in message text and in code comments.
- Open
-
DERBY-1835 SQL State Messages need to be reviewed and improved for clarity and completeness.
- Closed
-
DERBY-5878 Add message argument names, as comments, to English message file produced by MessageBuilder.
- Closed
-
DERBY-5890 Remove ij EXPECT command
- Closed
-
DERBY-5892 Help people create translatable messages by summarizing the rules which the translators follow.
- Closed
- relates to
-
DERBY-5832 Localize messages introduced or changed in 10.9.1
- Closed