Re: Localization with Struts/Tiles and URLs

[Ruth, Brice]

Our product content is going to be localized to the countries that the 
products are available in, and for that, we've built a database that 
holds this "content" and an interface to manage it - when adding a new 
translation, the user selects what language they're entering the 
translation for, and this is stored in the database - the keys used in 
the database to define the language are the same two by two codes used 
for locales (so en_US, fr_FR, etc.) so when pulling product data from 
the database into a JavaBean for the product (pseudo object-relational), 
the Bean has a collection of all the languages that this product is 
available in - this then can be rendered appropriately on the page in 
the user's locale.

Rajat Pandit wrote:

Hello,
A little off the topic though, but it this has always intrigued me about
building a multilingual website. I mean using the resources bundle u
could provide a translations from the labels but in case of building a
CMS (content management system) how would one enter the content in the
native language in which the site is translated?
I believe the solution that I have come up with is to save the same
content in different languages. But I am sure there would be a better
solution out there somewhere. I am new to struts development (and java
on the whole!) so pardon my ignorance!!.
rp

-----Original Message-----
From: Ruth, Brice [mailto:[EMAIL PROTECTED] 
Sent: Monday, October 20, 2003 9:41 AM
To: Struts Users Mailing List
Subject: Re: Localization with Struts/Tiles and URLs

Craig R. McClanahan wrote:

 

Ruth, Brice wrote:

   

[snip]
On the first point, our site will have a global landing page that 
will present the user with flags to choose their locale.
     

This is semi-offtopic, but might be of interest.

When I worked on a large scale multi-lingual app in Europe a few years
   

 

ago, my intent was to do exactly this (but with a tweak -- the landing
   

 

page language was determined by the browser's default language 
setting).  However, I was informed by more than a few Europeans that 
using flags for language choice was not being culturally sensitive -- 
if I'm a French-speaking person living in Belgium or Switzerland, it's
   

 

going to irritate me greatly to have to click the flag of France -- 
and it's not a 1:1 relationship for any multilingual country (as these
   

 

two, among others, are).

Craig
   

Craig,

Thanks - I'll pass this on to our marketing folks. One note, though - 
our site will not only be localized for language, but will also be 
sensitive to the actual products our company offers in those markets. 
So, if we market products in Belgium and France, and they aren't the 
same, then we'll have two flags - one for Belgium, one for France - 
though that obviously creates a problem with countries that have more 
than one language, like Belgium and Switzerland, for instance.

 

--
Brice D. Ruth
Sr. IT Analyst
Fiskars Brands, Inc.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]