UzLocal

Typography · § 9

Localization: adapting an interface to Uzbek

Localization (in Uzbek, mahalliylashtirish) is adapting a program, website, app or game for users of a particular language and country. It goes beyond translation: along with the text, the formats of dates and times, numbers and currency, addresses, phone numbers, names, images and examples are brought in line with local norms and habits. The result should feel as if the interface had been written in Uzbek from the start. The English term localization (L10n for short) is rendered in Uzbek as mahalliylashtirish; the form “lokalizatsiya” is best avoided.

How localization differs from translation

Translation only vs. localization
What changesTranslation onlyLocalization
Texttranslated word for wordmeaning and tone kept, sentence built the Uzbek way
Date11/16/20262026‑yil 16‑noyabr or 16.11.2026
Money$50; 1,500.5050 $; 1 500,50 (for an audience in Uzbekistan, 50 000 soʻm)
Names and addresses in examplesJohn Smith, Baker StreetAziz Karimov, Amir Temur koʻchasi, 15‑uy
Termsdifferent every timeconsistent, from the glossary

Language norm and script

An interface is written in literary Uzbek: dialect words may be unclear to people from other provinces, and the text should read equally naturally in any region. One product uses one script, Latin or Cyrillic, and never mixes them. In Latin script the letters oʻ and gʻ are written with ʻ (U+02BB), and the tutuq belgisi with ʼ (U+02BC). A straight apostrophe or a quotation mark in their place splits the word and breaks search and line wrapping (see the lesson on apostrophes).

Grammatical adaptation

Uzbek has no prepositions: their work is done by case suffixes and postpositions (koʻmakchi), and the predicate comes at the end of the sentence, so the structure of the source is not copied. There is no grammatical gender either: Russian forms such as “добавил / добавила” (he/she added) become a single qoʻshdi. After a numeral the noun stays singular (1 ta fayl, 5 ta fayl — 1 file, 5 files), so plural variants like English 1 file / 5 files are usually identical in Uzbek. The plural suffix -lar is normally used once per phrase: Hisob sozlamalari (Account settings), not Hisoblar sozlamalari.

Function words in interfaces
Source textRightWrong
От: / From:Kimdan:Dan:
Кому: / To:Kimga:Ga:
Открыть с помощью… / Open with…Ochish:… bilan ochish
Click “Download” to save the file to the disk.Faylni diskka saqlash uchun “Yuklab olish” tugmasini bosing.“Yuklab olish” tugmasini bosing, faylni saqlash uchun diskka.

Local formats

Formats for an Uzbek interface (details in the lesson on numbers, dates and currency)
FormatHow it is writtenNote
Full date2026‑yil 16‑noyabrnon-breaking hyphen after the number, month in lower case
Short date16.11.2026day.month.year
Time14:30; 10:00–18:0024‑hour clock, no AM/PM
Weekdushanba, seshanba … yakshanbastarts on Monday, day names in lower case
Numbers10 000; 2,5non-breaking space between thousands, decimal comma
Money50 000 soʻm; 50 $currency after the number
Phone+998 90 123‑45‑67country code +998

Cultural adaptation and terminology

Names, addresses and situations in examples should be familiar to Uzbek users: Aziz Karimov or Malika Yusupova sounds more natural than John Smith (agree such changes with the client). Currency, units of measurement and links are also checked against the audience. Terms come from the glossary and are used the same way throughout the product: if one screen says Sozlamalar (Settings) and another Parametrlar, users get lost. If a new text refers to an element that has already been translated, reuse its existing translation. Brand and product names are not translated; a case suffix is attached to them with ʼ or through a generic word.

Kamalak Payʼdan toʻlash or Kamalak Pay ilovasi orqali toʻlash (Pay with Kamalak Pay; a made-up name). Wrong: Kamalak Pay'dan, Kamalak Pay’dan, Kamalak Pay-dan. Konstruktorga oʻtish (Go to Builder): if the element was already translated as Konstruktor, do not write Builderʼga oʻtish.

Checking in context

Localization ends on the screen. Look at the translation in a screenshot or in the app itself: does the string fit, does the button match the heading, does the sentence still read correctly when a real value replaces the variable, are the date and number formats right? A separate string of 2–4 words without a full stop is most often a button or a heading; without context it is easy to translate it with a grammatical error, so when in doubt use the preview or ask the client.

UzLocal reference material. When quoting, please link to this page.

All lessons in this section

  1. §1Quotation marks: “ ” and inner ‘ ’
  2. §2Spaces and the non-breaking space
  3. §3Writing numbers, dates, times and amounts of money
  4. §4Em dash, en dash and hyphen
  5. §5Apostrophes: oʻ, gʻ (ʻ) and the tutuq belgisi (ʼ)
  6. §6Headings and capital letters
  7. §7Interface text: buttons, forms of address and tone
  8. §8Interface typography
  9. §9Localization: adapting an interface to Uzbek
  10. §10Abbreviations and acronyms: AQSh, MChJ, YTT