November 2002
Intermediate to advanced
560 pages
11h 16m
English
Often you may need to provide localized versions of your application or component, so that it can be used effectively in environments where U.S. English is not the primary language. You have probably already seen similar requirements with existing projects; the requirement to provide local versions of applications is certainly not unique to .NET.
Deploying a component for other locales involves two steps: internationalization and localization.
Internationalization (also known as i18n, because there are 18 letters between the initial i and final n in the word “internationalization”) enables a program to work effectively in all supported locales. Traditionally, it entails two steps:
Read now
Unlock full access