Based on my project experience on i18n I have summarized the steps to do i18n in a java project and the problems faced. Expect feedback on the post. http://ushathoughts.blogspot.com
Hi Usha, Welcome to Javaranch, I have rarely used i18n and most of the times UTF-8 encoding solves the problem also never experimented it with Struts, but when I had a glance of your blog, it seems to be a useful resource. I think you just need to say a bit of Localization in your blog to make things more clear.
Localization deals with restricting functionality based on organization/country.
Internationalization deals with making the app visible for different languages may be for the same country.
For instance if we have the app visible for 2 countries - US and CA. We can restrict the functionality using localization like showing zipcode for US and postal code for CA.
But i18n comes into picture when we want to show the same data for CA in english and French.
Hi, I admit that Localization and i18n and 2 different concepts. but I only thought that at times they might go hand in hand. And that addition might look good on your blog.
Campbell Ritchie
Sheriff
Joined: Oct 13, 2005
Posts: 32599
4
posted
0
Please don't say i18n; use the proper word. The explanation is to be found here.
Ulf Dittmer
Marshal
Joined: Mar 22, 2005
Posts: 35222
7
posted
0
#3 is an important one. Too often the layout is done with just a single language in mind. For your example, I'd say French text often needs up to 33% more horizontal space than English, sometimes even more. Tight layouts also need to consider the CJVK languages - those need more vertical space.
By the way, I wouldn't say that L10N is a restriction of functionality -more an adaptation to a particular locale-, while I18N is the process of making an application L10N-ready (without necessarily supporting more than one locale).
0
