Yeah, if you truly want to support internationalization, then you have to display all of your text with message keys.
-----Original Message----- From: Bailey, Shane C. [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 1:50 PM To: [EMAIL PROTECTED] Subject: Question for you Internationalization supporters I don't have a need right now to support Internationalization but if I do need to it seems like I would have to do much more than just the field names but whole page content must be done with message keys. I mean, what is the best way to support not just form field names with different languages using the message keys but whole page content that is say just a long description with no form on it. Every paragraph must be in a message resource. E.g. You must be doing this (not exact but abbreviated to shorten): file1.jsp: <bean:message key="app.welcome.header"/> <bean:message key="app.welcome.paragraph" /> <bean:message key="some.form.field" /> <bean:message key="app.welcome.footer"/> as opposed to doing this: file1_en.jsp: <!-Next lines are the header--> Hello! Here is the paragraph that welcomes you in English. <bean:message key="some.form.field" /> footer copyright 1999 where you would have to figure out how to display the correct file1_en.jsp as opposed to file1_fr.jsp. I guess the first way with EVERYTHING in a message resource is the only way to go? Just curious what the best way and any pit falls for supporting internationalization even with all the built in locale stuff already in the framework? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
