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.
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.
Joined: Oct 13, 2005
Please don't say i18n; use the proper word. The explanation is to be found here.
Joined: Mar 22, 2005
#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).