Crafting Global Connections Through Localization in 2025

Updated · 3 min read
On this pageThree terms, three jobsWhat localization covers beyond the wordsWhy internationalization comes firstWho does what, and whenWhere transcreation fits

A software company sends its English interface to a translator and gets back a perfect Korean file. Then the trouble starts. Buttons overflow. A sentence built from three strings comes out in the wrong order. Dates show as month-day-year, prices show two decimal places of won, and the sign-up form insists on a "first name" and "last name" in that order. The translation was fine. The product was not ready to be translated. That gap is what the translation vs localization question is really about.

Three terms get mixed up in every conversation about going international. Here is what each one means, who does it, and how it plays out for Korean.

Three terms, three jobs

Internationalization (i18n)

Designing and building a product so it can be adapted to other languages and regions without re-engineering. Done by designers and developers, before any translation.

Localization (l10n)

Adapting the product or content to a specific market: language, formats, units, images, legal text, examples. Done by translators and localizers, with product input.

Translation

Rendering the text into the target language. The core of localization, but only one part of it.

The W3C puts the relationship in one sentence: "Designers and developers internationalize products, so that they can be easily localized by translators and localizers." The abbreviations are just letter counts: 18 letters between the i and n of internationalization, 10 between the l and n of localization.

What localization covers beyond the words

The W3C lists what localization can involve beyond translating text, including numeric, date and time formats, currency, keyboard usage, sorting, symbols and colours, legal requirements, and address and name formats. For Korean, that list turns concrete quickly:

AreaWhat changes for KoreaTypical failure
DatesYear first, then month, then dayUS month-first dates copied into Korean text
CurrencyKorean won, normally without decimal placesPrices shown with ".00" or converted with rounding errors
NamesFamily name first, usually one field is naturalForms that require "first name" and "last name" in Western order
AddressesWritten from the largest unit to the smallest, with a postal codeWestern address templates that reorder or truncate fields
RegisterA deliberate choice of formality for each content typeMixed speech levels across screens
Legal textTerms, privacy notices and labelling adapted to Korean requirementsA translated foreign privacy policy that does not match local obligations

For the website side of this, see website localization for Korean customers.

Why internationalization comes first

The W3C notes that retrofitting a product for a global market "is obviously much more difficult and time-consuming" than designing it for one from the start. In practice, these are the internationalization issues that most often surface when a product goes Korean:

String concatenationCode builds: "Delete" + file name + "?"Korean puts the object before the verb, so the pieces must reorder. One complete string with a placeholder is the fix.
Particles after variablesA Korean particle attaches to a name inserted at runtimeThe correct particle depends on the last sound of the name. Code must handle it, or the text must be written to avoid it.
Hard-coded formatsDates and prices formatted in code with an English patternFormats should come from locale data, so Korean gets year-first dates and whole-won prices automatically.

Other common items: text stored in images, fixed-width buttons, fonts without full Korean character coverage, and sorting that assumes the Latin alphabet. None of these is a translation problem, and none can be fixed by a translator.

Who does what, and when

  1. Design and build: developers externalize strings, use Unicode throughout, take formats from locale settings, and avoid building sentences from fragments.
  2. Prepare: product and content teams write a glossary and style decisions (register, brand names) before translation starts.
  3. Translate: translators work with context: screenshots, string length limits, notes on placeholders.
  4. Localize: adapt images, examples, legal text and marketing to the Korean market; transcreate slogans where needed.
  5. Test: check the Korean build on real screens, with real names, addresses and prices.

Where transcreation fits

Some content needs more than localization: slogans, campaign lines, wordplay. That is transcreation, writing a new Korean line that does the same job. It sits at the far end of the same spectrum. We explain the differences between the service types in Korean language services explained and the method in transcreation for Korea. For software specifically, see Korean translation for software and apps, and for the broader strategic picture, localization versus globalization for the Korean market.

Preparing a product for Korean? We review your strings and screens for internationalization issues before translation starts, then translate and test in context. Contact us or see our services.

Work with us

Your site, ready for Korean users on day one.

Website and software localization into Korean, tested in context before launch.

Get a free quote