You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@struts.apache.org by bu...@apache.org on 2004/02/05 11:13:38 UTC

DO NOT REPLY [Bug 25536] - formatKey works incorrectly in

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=25536>.
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=25536

formatKey works incorrectly in <nested:write>

vspa@mail.ru changed:

------- Additional Comments From vspa@mail.ru 2004-02-05 10:13 -------
Imagine this scenario:

1. I have only one resource bundle file (default one). For whatever
reason.
2. In that file I have the following defined:
org.apache.struts.taglib.bean.format.int=#.##0
3. If a person with, say Dutch, locale
enters the site, he can use that format string perfectly, because there they use dot as grouping
separator. So <bean:write> tag works fine.
4. If a person with US locale enters the site he gets
exception, because this format string is not legal from US perspective (dot - is a decimal
separator there).

So what can be a solution in this case? Creating a copy of resource bundle
file is not an option. The only solution would be do not applyLocalizedPattern() if format string
is taken from res.bundle, but just always applyPattern(). So in every resource bundle format
strings should be specified in default not localized notation. What will you say?

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org