Hmmmm, we're developing with the space-is-cheap and they'll-always-want-something-different mentality.
As such, we have very few application-level strings and keep most at a page-scope. This way, when marketing wants one word changed it's a very small change to the resource bundle rather than having to go through the pages and change resource keys all over the place. Andrew -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 13, 2002 9:29 AM To: [EMAIL PROTECTED] Subject: Multi-language string resource strategy Hi All, in my previous applications whenever I wrote multiple strings for languages, I just wrote strings for each page and sorted them based on page, but now with the struts framework, basing it on pages doesn't really work. What do people do? I was thinking of some sort of dictionary-like listing, so when the application is bigger, you can scan through looking to see if the string you want to write already exists. Adam Find the best deals on the web at AltaVista Shopping! http://www.shopping.altavista.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
