I would keep to the former example of grouping by web page, since the text displayed on each page has its own separate context.
I would keep to the former example of grouping by web page, since the text displayed on each page has its own separate context. You could try to keep things DRY and identify all of the common text, but should the context of any page change, you may find yourself creating new resources that you would have already done if you kept the page resources separate. Another reason for keeping the resources separated by page is that if you ever need to translate your resources, the context for creating translations will be self-evident.
That helps you keep a clean separation of concerns, so your coders will not have to worry about how words might be translated, and your translators will not have to mess with any code.
Thanks, it makes a lot of sense what you said regarding the context of the page. – Ross Jun 9 at 16:05.
The first option may mean repeating texts, but is more flexible. What happens if, for example, company name is completely different from personal name? Or if tomorrow you boss decides that the label for the name of the company should change from "Name" to "Company name".
If you use the second option you are losing most of the advantages of using resource bundles.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.