l10n

dtsdwarak's picture

Join us for the Mozilla Localization Sprint at Chennai on February 19

You can say, one of the reasons why Mozilla has been hugely successful in its marketing, is because of Localization –Making software products available in local languages. Not many of them are good at English. And Localization gives a chance for people to use the software with local flavor and taste.

Sadly though, in a country like India, with many languages, there hasn’t been a very active contribution towards localization of Mozilla’s products.  So, in an attempt to bring in more contributors, Mozilla is organizing a series of L10N sprints across the country in various cities.  One such event happened in Pune last Sunday as a part of GNUnify’12 and Mozilla India Meet up.  Coming weekend, events are scheduled to take place, one in Bangalore (Saturday) and in Chennai (Sunday).

Brainchild behind this is, Rakesh ‘Arky’ Ambati, Mozilla’s Localization Community Manager, who will be visiting the cities and leading the events. Also expected are contributors from various local Linux Users’ Groups. Going by the way things happened at Pune, I can assure you that this is going to be really exciting!  Apart from people who are already into localization, this will be a great opportunity for budding enthusiasts and students who would like to contribute and get involved with Mozilla.

abhishek's picture

Domains in Your own language

I am sure that by now you would have at least seen one domain name which was written in a non-english language but still if you have not seen any such domain the screen shot below would explain the entire story. I would try to explain the mechanism behind these kind of Domain Names in this post

Domain Names which can be viewed in a language-specific script are known as Internationalized Domain Names or IDNs. This concept was introduced in December 1996 and was first implemented in 1998 but ICANN issued guidelines for the use of IDNA only in June 2003 any by today most of the TLDs support IDNs.

The Working

As we all know that a domain name has to resolve to an IP Address to function, but as language-specific domain names contains NON-ASCII characters and there are various limitations in their use, to overcome this basic limitation an encoding mechanism for such names is implemented by which this collection of  NON-ASCII characters are used to prepare a suitable character set which can be used, lets check the process with the following example

नागर.com  = xn--31b7aza8c.com

Subscribe to RSS - l10n