[
https://issues.apache.org/jira/browse/DERBY-5878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5878:
---------------------------------
Attachment: derby-5878-03-aa-addBracketedArgNumbersToComments.diff
Attaching derby-5878-03-aa-addBracketedArgNumbersToComments.diff. Committed at
subversion revision 1369040.
The translators asked me to add bracketed argument numbers to the comments in
the generated English properties file. So, instead of generating
# Arguments:
#
# connectionName
#
...we now generate
# Arguments:
#
# {0} = connectionName
#
Touches the following file:
M java/build/org/apache/derbyBuild/MessageBuilder.java
> Add message argument names, as comments, to English message file produced by
> MessageBuilder.
> --------------------------------------------------------------------------------------------
>
> Key: DERBY-5878
> URL: https://issues.apache.org/jira/browse/DERBY-5878
> Project: Derby
> Issue Type: Improvement
> Components: Build tools
> Affects Versions: 10.10.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-5878-01-aa-argsAsComments.diff,
> derby-5878-02-aa-commentElements.diff,
> derby-5878-03-aa-addBracketedArgNumbersToComments.diff
>
>
> The MessageBuilder program turns messages.xml into two output files:
> 1) The DITA source for the Reference Guide section on error messages.
> 2) The messages_en.properties file of engine messages.
> All of the translators I have dealt with want to use (2) as the English input
> for their translations. I believe this is because translators have written
> their own tools and those tools expect to work on properties files.
> Messages may have arguments. Those arguments appear as sub-elements of the
> messages in messages.xml. The arguments turn up in (1) but are thrown away
> when MessageBuilder produces (2). We can help translators do a better job by
> also writing the arguments as comments in (2).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
