This week's book giveaways are in the iOS and Features new in Java 8 forums.
We're giving away four copies each of Barcodes with iOS: Bringing together the digital and physical worlds and Core Java for the Impatient and have the authors on-line!
See this thread and this one for details.
The moose likes JSP and the fly likes industrial strenght internationalization Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Barcodes with iOS this week in the iOS forum
or Core Java for the Impatient in the Java 8 forum!

JavaRanch » Java Forums » Java » JSP
Bookmark "industrial strenght internationalization" Watch "industrial strenght internationalization" New topic
Author

industrial strenght internationalization

peter cooke
Ranch Hand

Joined: Mar 16, 2004
Posts: 317
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.

Peter Cooke


CIAO Peter M. Cooke
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 62101
    
  67

Or, Option 1.5:

Partition the project into sub-projects each with their own localization context. That way you end up with fewer, but logically partitioned, files.

It helps if the project has natural sub-divisions (as mine does), but you can create artificial ones if need be.
[ April 08, 2005: Message edited by: Bear Bibeault ]

[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: industrial strenght internationalization