This week's book giveaway is in the Other Open Source APIs forum. We're giving away four copies of Storm Applied and have Sean Allen, Peter Pathirana & Matthew Jankowski on-line! See this thread for details.
My compay is converting it's web presence from CGI script to JSP/Servlet using JSF or STRUTS. Currently the CGI scripts generate around 10,000 web pages. I would guess that probably a hundred or more pages are changed on a weekly basis.
During the conversion the company also wants to internationalize the content based on the user's location.
As I see my options for internationalizing the conent are below. Am I missing somehting?
Option 1) 1 resource bundle for 10,000 web pages and replicated per language. As I see it, the Content providers will be killing each other to insert their content changes. And the file would be gargantuan.
Option2)Provide a bundle for each specific page, and then replicate each bundle to the various langages. Allows web developers to effectively manage web page content, but adds tons files to the file system.
Option3) Place the all of the web pages content in an XML file. use something like a role tag to say this is the english conent or french conent. Then use XSLT to write the language specific content to the response.