How software breaks in other languages, and how to fix it.
21 practical chapters for engineers, designers, and product managers who are new to localization. No prior background is required. Each chapter explains one problem in plain language, lets you test it in a live interactive demo, and ends with a real production incident.
New to localization? Start with these five chapters
These five chapters take about 35 minutes in total. They explain the basic terms, show the three bugs users notice first, and demonstrate how to test an interface before paying for translation.
Step 1 · ~6 min
Orientation
Standards & architecture
Step 2 · ~6 min
Text Expansion
String length & responsive layout
Step 3 · ~8 min
Locale Formatters
Numbers, dates & currencies
Step 4 · ~10 min
Plurals and Gender
Plural rules, ordinals & gender
Step 5 · ~6 min
Pseudolocalization
Pre-translation UI testing
Already know the basics? Jump to any part below, or open Chapter 21 to run the audit and find twelve planted bugs across three localized markets.
Stakeholder Learning Paths
Choose your role to get targeted chapters and meeting checklists
Product Managers
Scoping, budgets, quality gates, and market readiness
Separate one-time engineering architecture from recurring translation costs. Enforce Translation Memory reuse to lower costs and set objective MQM quality thresholds.
Questions to ask in your next review
- 1.Are we budgeting i18n engineering separately from per-language translation spend?
- 2.Are we leveraging Translation Memory (TM) to avoid re-paying for repeated strings?
- 3.Does our contract with localization vendors establish objective MQM quality scoring?
Priority Chapters for Product Managers (6 chapters)
Orientation
Standards & architecture
Text Expansion
String length & responsive layout
Plurals and Gender
Plural rules, ordinals & gender
Translation Pipeline
String extraction, file formats & memory
LQA Scoring
Translation quality review & MQM
The Audit
Finding 12 bugs on a checkout screen
Localization Novice Cheat Sheet
The 5 Golden Rules of Localization
Core concepts every product manager, designer, and engineer should master before shipping.
Never concatenate strings
Word order changes across languages. Concatenation locks grammar into English sentence structure.
Budget 30% to 100%+ text expansion
German and Portuguese double the length of short English actions, clipping fixed-width containers.
Plurals are grammatical classes, not binary checks
Russian has 4 plural categories, Arabic has 6, and French treats 0 as singular category one.
Mirror layouts in RTL, but never mirror clocks or media controls
Reading flow inverts from right to left, but universal physical metaphors remain standard.
Test with pseudolocalization before spending on translation
Exposes hardcoded strings, truncated containers, and missing fonts instantly during development.
Part 1
Getting Oriented · Terms, standards, and architecture
Learn the difference between internationalization (i18n) and localization (l10n), and see how four core standards work together to display text in any language.
Part 2
Common UI Defects · Text expansion, formatting, and plurals
Start with the three bugs users notice first in a translated app. Translated labels overflow their buttons, numbers and dates show the wrong regional format, and plural sentences break grammar rules.
- 02Text ExpansionStart hereString length & responsive layout~6 minShows why translated labels often grow wider or taller than English text and break fixed-size containers. In the demo, you resize a button across German, Russian, Finnish, and Thai to see where the layout overflows.
- 03Locale FormattersStart hereNumbers, dates & currencies~8 minExplains how different regions format numbers, prices, dates, and measurement units using built-in browser APIs. The demo formats the same values across multiple locales to compare decimal separators, currency symbols, and date order.
- 04Plurals and GenderStart herePlural rules, ordinals & gender~10 minShows why checking if a count equals one fails in languages with three, four, or six plural forms. The demo steps through item counts and grammatical gender in English, Russian, Polish, Arabic, and French.
Part 3
The Intl Toolbox · Lists, sorting, time zones, calendars, and fallback
Modern browsers and runtimes include built-in rules for hundreds of locales. These chapters show how to format lists, sort names alphabetically, convert time zones, display local calendars, and pick a fallback language.
- 05Lists and RangesCoreLists, date ranges & durations~6 minExplains why joining words with commas and a hardcoded 'and' breaks in other languages. The demo formats item lists, date ranges, and time durations across locales using built-in browser formatters.
- 06SortingCoreAlphabetical order & search~6 minShows how alphabetical order changes from one language to another and why default code sorting puts accented letters in the wrong place. The demo sorts the same list of names under German, Swedish, Polish, and Spanish rules.
- 07Time ZonesCoreOffsets, DST & IANA zones~8 minExplains why storing a fixed UTC offset fails when daylight saving time starts or governments change their clocks. The demo converts a meeting time across global cities and steps through daylight saving gaps and 45-minute offsets.
- 08CalendarsDeep diveCalendar systems, eras & week start~8 minShows how countries count years using different calendar systems and start the week on Monday, Saturday, or Sunday. The demo converts a single date into Buddhist, Islamic, Hebrew, and Japanese imperial calendars.
- 09Locale FallbackCoreLanguage matching & fallback chains~8 minExplains how an app chooses the closest available language when it does not support a user's exact locale. The demo compares three matching methods to show why dropping a region tag can accidentally switch Chinese scripts.
Part 4
Scripts and Layout · Line wrapping, fonts, and reading direction
Many writing systems do not follow English layout rules. Chinese, Japanese, and Thai wrap lines without spaces between words, while Arabic and Hebrew read from right to left and mirror the page layout.
- 10Line BreakingDeep diveWrapping rules & word boundaries~7 minShows how browsers wrap lines in languages like Chinese, Japanese, and Thai that do not put spaces between words. The demo narrows a text container across scripts to show punctuation rules and dictionary word breaks in action.
- 11CJK Font FallbackDeep diveFont selection & shared Han characters~7 minExplains why Chinese, Japanese, and Korean share the same character codes for many ideographs but draw them differently. The demo switches language tags on the same text to show how the browser picks the right regional font.
- 12Bidirectional TextDeep diveMixing right-to-left & left-to-right text~10 minShows what happens when left-to-right English names, numbers, or URLs appear inside right-to-left Arabic or Hebrew sentences. The demo demonstrates how punctuation jumps to the wrong side and how invisible isolation markers fix the reading order.
- 13RTL MirroringCoreMirroring layouts & icons for RTL~8 minExplains how an entire app layout flips from right to left for Arabic and Hebrew readers. The demo switches an interface between English and Arabic to show which CSS properties mirror automatically and which icons should flip.
Part 5
Strings, Names, and Input · Characters, file encodings, numbers, and forms
User input breaks when code assumes English letters and US forms. These chapters explain how computers store characters and bytes, how to read numbers typed with commas, and how to build global name and address forms.
- 14Unicode StringsCoreCharacters, graphemes & normalization~8 minShows why a single visible character or emoji can take up multiple units in memory and break string length checks. The demo inspects accented words and emoji to compare byte counts, code points, and visible characters.
- 15Character EncodingDeep diveUTF-8 bytes & garbled text~7 minExplains how computers store text as bytes and why reading a UTF-8 file with the wrong encoding turns letters into garbled symbols. The demo encodes text into raw bytes and decodes it with legacy tables to reproduce the corruption.
- 16Input ParsingCoreReading user-typed numbers & digits~7 minShows why standard JavaScript number parsers fail or lose digits when users type commas as decimal separators or use non-Latin numerals. The demo runs German prices and Arabic digits through standard parsers and a locale-aware parser.
- 17Names and AddressesCoreGlobal name order & address forms~8 minExplains why forms that require a first name, last name, state, and numeric ZIP code reject real users in many countries. The demo tests international names and postal addresses against a strict US form and a flexible global form.
Part 6
Shipping Translations · Translation files, testing, quality review, and the audit
Moving text from code to translators and back requires a reliable workflow. These chapters cover translation files and memory, pre-translation UI testing, translation quality scoring, and a final audit of a broken checkout screen.
- 18Translation PipelineCoreString extraction, file formats & memory~9 minFollows a piece of UI text from source code into translation files and back into the app. The demo compares industry file formats (gettext PO, XLIFF, and ICU JSON) and shows how translation memory reuses past translations.
- 19PseudolocalizationStart herePre-translation UI testing~6 minShows how to test an app with automatically generated fake translations before paying human translators. The demo converts English strings into accented, stretched, and right-to-left text so you can spot hardcoded strings and clipped buttons immediately.
- 20LQA ScoringCoreTranslation quality review & MQM~12 minExplains how teams grade translation quality objectively instead of arguing over opinions. In the demo, you review ten translated German checkout strings, log errors by category and severity, and calculate whether the batch passes quality thresholds.
- 21The AuditAuditFinding 12 bugs on a checkout screen~15 minPuts the whole guide into practice on a realistic checkout page launched in Germany, Saudi Arabia, and Japan. You inspect the live screen, flag twelve planted localization bugs across all three markets, and compare your findings with the answer key.