Internationalization in technology

Difficulties

In making software products, internationalization and localization pose challenging tasks for developers, particularly if the software is not designed from the beginning with these concerns in mind. A common practice is to separate textual data and other environment-dependent resources from the program code. Thus, supporting a different environment, ideally, only requires change in those separate resources without code modification; greatly simplifying the task.

The development team needs someone who understands foreign languages and cultures and has a technical background; such a person may be difficult to find. Moreover, the duplication of resources could be a maintenance nightmare. For instance, if a message displayed to the user in one of several languages is modified, all of the translated versions must be changed. Software libraries that aid this task are available, such as gettext.

Since open source software can generally be freely modified and redistributed, it is more apt to internationalization. Most proprietary software is only available in languages considered to be economically viable whereas the KDE project, for example, has been translated into over 70 languages.

Methods

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.

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. However, many development environments still lack full Unicode support, which drastically hampers the translation effort, especially to East Asian languages.

Relation to globalization

Internationalization is sometimes used interchangeably with globalization to refer to economic and cultural effects of an increasingly interconnected world.

While internationalization most commonly refers to the addition of a framework for multiple language support, especially in software, it sometimes refers to the process whereby something (a corporation, idea, highway, war, etc.) comes to affect multiple nations. This usage is rare; globalization is preferred. Because of globalization, many companies and products are found in multiple countries worldwide, giving rise to increasing localization requirements.

Localization may describe production of goods nearer to end users to reduce environmental and other external costs of globalization.

Relation to localization

In software development, after a product has been internationalized, "localization" refers to the process of making it ready for a specific market.

So you can refer to a product as being "internationalized" if it has been developed to meet most of the needs of an international community, but not yet customized to a specific region. The customization to a specific region is called "localization".

Copyright 2008 - France BtoB from Wikipédia