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=21992>. 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=21992 Localized number formatting inconsistency ------- Additional Comments From [EMAIL PROTECTED] 2004-01-02 21:44 ------- IMHO, this functionality is correct and appropriate as it is. If the format pattern is in a resource file, then it *should* be the localised pattern. If you sent off your resource files to an external translator, as many (most?) companies do, you don't want to have to point out which entries are supposed to be format patterns and therefore not translated. You want them to translate everything in the resource file. So format patterns will be translated, and therefore no longer contain placeholders, but "real" values. By the way, it is important to note that, when you specify the format pattern in the JSP page itself, you are *not* specifying the "English" format, as Emmanuel suggests. These are *placeholder* values. You can think of the substitution, in the US case, as being effectively a no-op, because the "real" values happen to be the same as the localised values, but *it is still a translation* from placeholders to real values. The documentation of the placeholders is in the Javadoc for DecimalFormat, although it isn't very clear about the placeholder versus real value issue. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
