• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

industrial strenght internationalization

 
Ranch Hand
Posts: 317
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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 ]
reply
    Bookmark Topic Watch Topic
  • New Topic