Personally, I would have thought that per-page resources would introduce
more problems than they solve. If there is text that needs to be consistent
across pages, it's much better to have it in only one place. Even if keys
are the same across pages, there is no assurance that the text will be. And
when it comes to translation time, all those strings will have to be
translated multiple times - and perhaps not always the same way, especially
with multiple translators working on a large app.

Just my 2 cents...

--
Martin Cooper


----- Original Message -----
From: "Jonathan Asbell" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 30, 2001 8:01 PM
Subject: Re: Resources clarification - is there a work around


> Thanks Pete.  However it just seems strange that Struts just offers one
big
> resource file for each Local.  I have developed 3 international sites, and
I
> can safely say that when a set of resources are associated with a
particular
> page it is much easier to manage than 1 resources for all pages.  Has
anyone
> hacked at the Struts code to get around this?  I dont like the
concatenating
> idea because it is too easy to have duplicates; and you probably want to
use
> the same resource names anyway to keep a consistency.  Anyone else have
any
> ideas?
>
> ----- Original Message -----
> From: "Peter Alfors" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, May 30, 2001 9:33 AM
> Subject: Re: Resources clarification :^)
>
>
> > You could combine all of your property files during your build.
> > This would allow you to have as many different property files as you
> > want.
> > However, you need to be careful that you do not have duplicate names
> > across multiple files.
> >
> > HTH,
> >     Pete
> >
> > Jonathan wrote:
> >
> > > Hello all.  It appears that the ActionServlet points to a resources
> > > file, and not a ResourceBundle object. Is this true?  The reason is
> > > that I would like to group in the same directory the following:1) a
> > > particular ActionForm2) the Action class that works with that
> > > ActionForm3) the resources (strings) that work with that
> > > ActionForm The reason is that it is much easier to manage the
> > > artifacts on a page by page basis.How can I do this
> > > properly ThanksJonathan
> >
>


Reply via email to