DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13934>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13934
Translate task shouldn't load default locale properties
Summary: Translate task shouldn't load default locale properties
Product: Ant
Version: 1.1
Platform: All
OS/Version: Windows NT/2K
Status: NEW
Severity: Enhancement
Priority: Other
Component: Optional Tasks
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: Eric.Smith@NextPage.com
Suppose I'm using the Translate task to create localized versions of an HTML
page from a locale-neutral source. If I am working on a U.S. English system,
but attempting to target the German translation, I may end up getting English
strings in my final output, because the Translate task always tries to load
strings for the system default locale in addition to the locale specified in
the task attributes.
Specifically, if I add a new string key to the source HTML file, and add the
key to the U.S. English property file, but forget to add the key to the German
property file, the task will succeed, inserting English into the German HTML
page. I don't think this is ever the right behavior. I'd rather have the task
fail -- automatically detecting the problem instead of requiring visual
inspection of the final HTML.
In the case where a string should be used for all locales, it should go in the
base bundle property file.
If there really is a situation where you always want the default locale, maybe
an attribute could be added to override that behavior, with a default value to
preserve backward compatibility.
--
To unsubscribe, e-mail: <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
|