218
edits
Note: Currently new registrations are closed, if you want an account Contact us
m (Protected "Localization and Internationalization": Excessive spamming ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))) |
|||
(21 intermediate revisions by 3 users not shown) | |||
Line 5: | Line 5: | ||
-[[wikipedia:Genesis|Genesis]] | -[[wikipedia:Genesis|Genesis]] | ||
==Introduction== | |||
The Software industry started in US,and traditionally software that allows only English input and output has been forced upon global users. This is based on this question from developers: "Why can't they all speak English?". However if a user is given two software products that offer same features, most people would choose one in their native language. | |||
Now a days software development centers are concentrated in countries like India, Australia, Mexico and Israel. As software is developed in different parts of world, successful companies believe that it is critical that their software products interact with their users in their native language and local conventions. Monolingual and mono cultural software products are not competitive. | |||
Let us illustrate the problem of monolingual programming practice by an example. | |||
Below given is a program to check the valid inputs from a user. | |||
char c; | |||
//Get user input | |||
if((c>='A' && c<='Z') || (c>='a' && c<='z')){ | |||
//Accept the input | |||
}else{ | |||
//Error Handling | |||
} | |||
What is the problem with this code? This code is wriiten in the assumption that users are going to input english text and letters are between A to Z. The above code will not work in Danish. Danish alphabet has 3 more letters after Z. This will frustrate Danish users. Now imagine what would happen if a chinese user tried to enter data? | |||
Converting an American software package into a multi-lingual product or "Americanizing" foreign software entails more than translation. A properly localized software package allows the local user to exploit the software's power to do exactly the same things that the original software does for the original user, but according to the local user's own rules and conventions. The local user will not be distracted by imprecise or ambiguous features that can result from inadequate attention to cultural and linguistic differences, nor from the nature of the software and engineering constraints on equipment. | |||
Around the world local conventions exist for number formatting, currency, dates, times, names, addresses, measurement, calendar. Besides local conventions software developer must consider cultural diversity issues related to numbers and colors. In Asian countries white denotes death in general but in western countries it is black. In Latin America death is denoted by purple. In US 13 is considered unlucky, 69 has sexual connotations, and 666 is the sign of the devil. In Hong Kong the number 7 is unlucky, while in India some people consider 7 as lucky number. | |||
Even English is not same across the world. See the following examples: | |||
''' US english''' ''' UK english''' | |||
Aluminum Aluminium | |||
Center Centre | |||
Internationalization Internationalisation | |||
Flavor Flavour | |||
Tire Tyre | |||
Elevator Lift | |||
Hood Bonnet | |||
Mutual Fund Unit Trust | |||
Pavement Road | |||
Sidewalk Pavement | |||
Trunk Boot | |||
Mere translation of the strings will not solve the problem. See the following examples. | |||
Here are signs from hotels around the world showing what can happen if you don't have knowledgeable translators: | |||
''Please leave your values at the desk'' - France | |||
''You are invited to take advantage of the chambermaid''- japan | |||
''Ladies are requested not to have children at the bar''- Norway | |||
==Customized Localization== | ==Customized Localization== |