Recommended practices for managing s2 resources bundles

[Jeromy Evans <je...@blueskyminds.com.au>]

Struts 2 is very flexible when it comes to organizing resource bundles 
for i18n.
Is anyone experienced with i18n issues in a *large* struts 2 application 
able to share what you've found to be an effective way to organize these 
resources? And preferably why you've arrived at that conclusion?

eg. global resources vs package vs action vs model, consistent naming 
conventions, use of the text and i18n tags

I know the answer is "it depends" which is why I'm especially interested 
in the why part of the answer.  Any insight you can provide will be 
greatly appreciated!

regards,
 Jeromy Evans

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

Re: Recommended practices for managing s2 resources bundles

[Wes Wannemacher <we...@wantii.com>]

Jeromy,

I haven't done this on a large Struts2 project, but I have worked on a
rather large scale app that required il8n... One thing to consider is
the frequency that you might change or add translations. In a perfect
world, you'll get them all right the first time, but you're bound to
find some screw-ups, so consider rolling your own DefaultTextProvider so
that you can change translations w/o reloading all the resources.


On Sun, 2008-02-24 at 12:42 +1100, Jeromy Evans wrote:
> Struts 2 is very flexible when it comes to organizing resource bundles 
> for i18n.
> Is anyone experienced with i18n issues in a *large* struts 2 application 
> able to share what you've found to be an effective way to organize these 
> resources? And preferably why you've arrived at that conclusion?
> 
> eg. global resources vs package vs action vs model, consistent naming 
> conventions, use of the text and i18n tags
> 
> I know the answer is "it depends" which is why I'm especially interested 
> in the why part of the answer.  Any insight you can provide will be 
> greatly appreciated!
> 
> regards,
>  Jeromy Evans
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
> 


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