Internationalization and localization
In computing, internationalization and localization (American spelling) or internationalisation and localisation (Commonwealth spelling) are ways of changing software so it works with different languages, regions, and needs. They are often shortened to i18n and l10n.
Internationalization is the process of designing a software program so that it can be changed for many languages and regions. This works without having to change how the program is built. Localization is the process of changing internationalized software for one specific region or language. This is done by translating the text and adding parts that fit that locale.
Localization can be done many times, once for each locale. It depends on the flexible design that internationalization provides. Internationalization is ideally done just once, before localization begins, or as a natural part of ongoing development.
Naming
People often shorten these long words to numeronyms. i18n stands for internationalization. There are 18 letters between the first "i" and the last "n." This short form was first used at Digital Equipment Corporation in the 1970s or 1980s. l10n stands for localization. Some writers capitalize it as L10n so the two are easier to tell apart. Some companies, like IBM and Oracle, use the word globalization (g11n) to mean internationalization and localization together.
Microsoft describes internationalization as world-readiness plus localization. World-readiness means the developer makes a product work with many writing systems and cultures. It also means keeping the text on screen in a form that can be localized (localizability, shortened to L12y). Hewlett-Packard and HP-UX created a system called "National Language Support" or "Native Language Support" (NLS) to help make software that can be localized. Some companies, including IBM, use the term National Language Version (NLV) for a version of a product made for one specific locale. This suggests that other similar versions exist for other markets.
Software can be designed to work with many languages and places. This is called internationalization. Adapting it for a specific language or region is called localization. Translation is usually the most time-consuming part of language localization. It can include dubbing or subtitles for films and videos, translating printed text and digital media, and changing images and logos that contain words. Writing customs also differ. These include the decimal separator, digit grouping, Date and time format, and writing systems that go in different directions. The Common Locale Data Repository from Unicode collects many of these differences so they can be handled more easily.
Countries also differ in everyday details, such as paper sizes, telephone number formats, currency, system of measurement, and Time zones. Laws can be different too, so a product may need changes for each place. Culture matters as well. This includes Local holidays, Personal name and title conventions, and local customs and conventions.
Business process for internationalizing software
To internationalize a product, it is important to look at the many markets where it might be used. Some details make this a big job. For example, the address fields may need to be a different length, addresses may be written in different formats, and some countries do not have postal codes or states. New sign-up steps that follow local laws also add to the work. A broader approach also thinks about culture, such as how business processes are changed and how people in different places behave.
Already in the 1990s, companies such as Bull used machine translation (Systran) on a large scale for all their translation work. Human translators helped by preparing the text so the computer could read it, and by post-editing the results.
Engineering
When a program is made to work in many languages and places, each part that might change from place to place is kept in its own separate module. This includes code, text, and data. A module can use a standard library, or it can be swapped out for each region. Programs often store text in resource files, which the program loads while it runs. These text files are fairly easy to translate. The place where translated text is kept is sometimes called a message catalog. One software library and format that helps with this is gettext.
To support several languages, a program must pick the right language file while it runs. The parts of the code that check typed information and handle other local data must also work with different regional needs. Modern development tools and operating systems include advanced libraries for this. See also Standard locale data above. Some changes, such as the direction of writing or how text is sorted, need bigger changes than translation alone. For example, OpenOffice.org handles this with compilation switches.
Process
After planning, a globalization method has three steps: internationalization, localization, and quality assurance. Development teams often include someone who handles the basic parts of the process, which helps all the other steps happen. These people usually know foreign languages and cultures and have some technical knowledge. Technical writers are needed to write wording that fits each culture, and engineers are needed to set up and test the local parts of the software.
Once software is properly internationalized, it can be localized in more spread-out ways. Free and open source software is often localized by users and volunteers, sometimes working in teams. The GNOME project, for example, has volunteer translation teams for over 100 languages. MediaWiki supports over 500 languages, and about 100 of them are mostly complete as of September 2023. Translating existing text is hard to keep up to date, because if a message shown to the user changes, every translated version must change too. Independent software vendors such as Microsoft may provide localization guidelines for developers. The language used for software localization may also be different from the written language.
Commercial considerations
In business, localization helps companies reach more markets. In the early 1980s, Lotus 1-2-3 took two years to separate its program code from its text, and it lost its lead in Europe to Microsoft Multiplan. By 1985, about a quarter of Ashton-Tate's $80 million in yearly sales came from outside the United States. The company translated its products into 11 European languages. MicroPro used an Austrian translator for the West German market, and the WordStar manual ended up with a tone that an executive said it should not have had. When Tandy Corporation needed French and German versions of English error messages for the TRS-80 Model 4, its Belgium office and five translators in the US made six different versions. The versions changed depending on the gender of computer parts.
Localization also costs a lot, and the costs go well beyond engineering. Businesses must change how they make, store, and ship many separate localized products. These products are often sold in different currencies, under different laws, and with different tax rules. Sales, marketing, and technical support teams must also work in the new languages to help customers. For small language groups, it may never be worth offering a localized product. Even when a large language group could make it worthwhile, a software company may not be big or skilled enough to handle the extra work of operating in many regions.
Examples and counterexamples
One example of a localization problem is Microsoft's effort to keep some keyboard shortcuts useful in local languages. In the Italian version of Microsoft Office, some programs use "CTRL + S" (sottolineato) instead of "CTRL + U" (underline). Most people expect "CTRL + S" to mean "Save." Before 'AutoSave' arrived, this could leave many underlined words in an unsaved document.
The team that worked on Microsoft Excel translated the tokens used in formulas when they changed number and date formats for each language. For example, =SUM(A1:A10) becomes =SOMME(A1:A10) in French or =SUMME(A1:A10) in German. This made formulas easier for people who do not know English. However, searching the internet for help was harder. Before machine translation of web pages, examples from other languages were hard to find. Manuals and tutorials had to translate every formula in their examples and exercises.

Quiz time!
4 questions about Internationalization and localization
Why is internationalization sometimes shortened to i18n?
Keep exploring
This article is a child-friendly adaptation of the Wikipedia article on Internationalization and localization, available under CC BY-SA 4.0.
Images from Wikimedia Commons. Tap any image to view credits and license.