Internationalization

Internationalization and Globalization

In computing, internationalization and localization are means of adapting computer software to different languages and regional differences. Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. Localization is the process of adapting software for a specific region or language by adding locale-specific components and translating text. Due to their length, the terms are frequently abbreviated to the numeronyms i18n, where 18 stands for the number of letters between the i and the n in

Internationalization :

The capital L on l10n helps to distinguish it from the l and N in Localization.

Language Localisation :

Language localisation is the process of translating a product into different languages or adapting a language for a specific country or region. This article focuses on the latter. Many languages, especially world languages with a large number of native speakers, have spread geographically and are nowadays used in many countries and regions. Thus, different national varieties of these languages have evolved. Linguistic differences include pronunciation, spelling conventions and grammatical patterns. It is important for companies to take such differences into account, for example, when creating websites for specific regional markets.

English Language Localisation :

The two largest countries (in population) where English is spoken natively are the United States and the United Kingdom. There are numerous differences between American English and British English-spelling conventions (color, center, program, localization vs colour, centre, programme, localisation), pronunciation, words with different meanings, vocabulary and slightly different grammar patterns particularly in the use of tenses. Localisation in this context usually refers to creating country-specific websites or publishing different editions of a book.

Focal points of internationalization and localization efforts include :

Language :

.

Culture :

Culture :

• Images and colors: issues of comprehensibility and cultural appropriateness Names and titles
• Government assigned numbers (such as the Social Security number in the US, National Insurance number in the UK, Isikukood in Estonia) and passports
• Currency (symbols, positions of currency markers)
• Weights and Measures
• Paper Sizes

Writing Conventions :

Writing Conventions :

• Date/time format, including use of different calendars
• Time zones (UTC in internationalized environments)
• Formatting of numbers (decimal points, positioning of separators, character used as separator)
• Any other aspect of the product or service that is subject to regulatory compliance

.

The distinction between internationalization and localization is subtle but important. Internationalization is the adaptation of products for potential use virtually everywhere, while localization is the addition of special features for use in a specific locale. Internationalization is done once per product, while localization is done once for each combination of product and locale. The processes are complementary, and must be combined to lead to the objective of a system that works globally, Subjects unique to localization also include.

Language Translation :

• National varieties of languages
• Special support for certain languages such as East Asian languages
• Local Customs
• Local Content
• Symbols
• Order of sorting
• Aesthetics
• Cultural values and social context

Business process for internationalizing software :

Business process for internationalizing software

In order to internationalize a product, it is important to look at a variety of markets that your product will foreseeably enter. Details such as field length for street addresses, unique format for the address, ability to make the zip code field optional to address countries that do not have zip codes, plus the introduction of new registration flows that adhere to local laws are just some of the examples that make internationalization a complex project.

A broader approach takes into account cultural factors regarding for example the adaptation of the business process logic or the inclusion of individual cultural (behavioral) aspects.

Coding practice :

Coding practice

The current prevailing practice is for applications to place text in resource strings which are loaded during program execution as needed. These strings, stored in resource files, are relatively easy to translate. Programs are often built to reference resource libraries depending on the selected locale data. One software library that aids this is gettext. No prior internationalization need be in place.

Thus to get an application to support multiple languages one would design the application to select the relevant language resource file at runtime. Resource files are translated to the required languages. This method tends to be application-specific and, at best, vendor-specific. The code required to manage date entry verification and many other locale-sensitive data types also must support differing locale requirements. Modern development systems and operating systems include sophisticated libraries for international support of these types.

Difficulties :

Difficulties

While translating existing text to other languages may seem easy, it is more difficult to maintain the parallel versions of texts throughout the life of the product. For instance, if a message displayed to the user is modified, all of the translated versions must be changed. This in turn results in a somewhat longer development cycle. Many localization issues (e.g. writing direction, text sorting) require more profound changes in the software than text translation. For example, OpenOffice.Org achieves this with compilation switches.

To some degree (e.g. for Quality assurance), the development team needs someone who understands foreign languages and cultures and has a technical background. In large societies with one dominant language/culture, it may be difficult to find such a person.

One example of the pitfalls of localization is the attempt made by Microsoft to keep some keyboard shortcuts significant in local languages. This has resulted in some (but not all) programs in the Italian version of Microsoft Office using "CTRL + S" (sottolineato) as a replacement for "CTRL + U" (underline), rather than the (almost) universal "Save" function.

Costs and benefits :

Costs and benefits

In a commercial setting, the benefit from localization is access to more markets. However, there are considerable costs involved, which go far beyond just engineering. First, software must generally be re-engineered to make it world-ready.

Then, providing a localization package for a given language is in itself a non-trivial undertaking, requiring specialized technical writers to construct a culturally appropriate syntax for potentially complicated concepts, coupled with engineering resources to deploy and test the localization elements. Further, business operations must adapt to manage the production, storage and distribution of multiple discrete localized products, which are often being sold in completely different currencies, regulatory environments and tax regimes.

Finally, sales, marketing and technical support must also facilitate their own operations in the new languages, in order to support customers for the localized products. Particularly for relatively small language populations, it may thus never be economically viable to offer a localized product. Even where large language populations could justify localization for a given product, and a product's internal structure already permits localization, a given software developer/publisher may lack the size and sophistication to manage the ancillary functions associated with operating in multiple locales. For example, Microsoft Windows 7 has 96 language packs available.

One alternative, most often used by open source software communities, is self-localization by teams of end-users and volunteers. The KDE3 project, for example, has been translated into over 100 languages, and KDE4 is available in 68. However, self-localization requires that the underlying product first be engineered to support such activities, which is a non-trivial endeavor.