Localization (software)
Internationalising software: string extraction, ICU messages, locale formats, translation files.
Download all 19
- App localisation track
Takes an English-only app to its first extra language in gated steps, from readiness scan and string extraction to formatting fixes, pseudo-localisation, translation hand-off and linguistic QA.
- Automate translation file sync
Designs the pipeline between a repo and translators, with key extraction, upload to a translation system or vendor, download of finished locales, CI checks for keys and fallbacks, and approvals.
- Build a localization glossary
Builds a product term base from UI strings, with definitions, do-not-translate terms and proposed translations per locale, so localization stays consistent. Use before the first translation round.
- Design international name and address fields
Designs form fields, validation and storage for personal names, postal addresses and phone numbers that work across countries. Use for international sign-up, checkout or shipping forms.
- Design locale detection and routing
Designs how a web or mobile app picks and remembers language and region, with negotiation, explicit choice, URL strategy, hreflang, fallback chains and language kept separate from currency.
- Extract hard-coded UI strings
Finds hard-coded user-facing strings and moves them into an i18n catalog with meaningful keys and translator comments, without changing behaviour. Use when preparing an app for translation.
- Internationalisation-ready code rules
Standing rules that keep any user-facing code an assistant writes translatable, with catalog strings, ICU plurals, no concatenation, locale-aware formatting, logical CSS and no text in images.
- Implement locale-aware sorting and search
Implements locale-aware sorting, comparison and search with ICU collation, Unicode normalisation, case folding, accent-insensitive matching and database collations, plus tests that break naive code.
- Implement locale-aware formatting
Replaces hand-built date, time, number, currency, percentage and list formatting with locale-aware platform APIs across a codebase, and adds tests that run in several locales.
- Localization engineer
Localization engineer who builds software that ships in many languages, with catalogs and ICU messages, CLDR formats, bidi, pseudo-localisation, translation pipelines and linguistic QA.
- Localise game strings and fonts
Plans and implements game localisation, covering string tables, variables and plurals, font atlases for CJK and Cyrillic, text expansion in fixed UI, subtitles and platform language rules.
- Plan a new language launch
Plans adding one more language or market to an already localised app, with translation effort, formats, legal and support content, store listings, native QA, flagged rollout and a checklist.
- Plan and implement right-to-left support
Plans and implements right-to-left layout support (logical properties, mirroring rules, bidi text, icons) for a web or mobile UI. Use when adding Arabic, Hebrew, Persian or Urdu.
- Pseudo-localize the UI
Adds a pseudo-localisation build or mode that expands, accents and brackets strings to reveal truncation, concatenation and hard-coded text, then lists the issues found by screen.
- Review code for internationalization bugs
Reviews code for internationalization bugs such as concatenated strings, hard-coded date, number and currency formats, naive plurals, text expansion and RTL breakage. Use before adding new locales.
- QA a translated string catalog
QA-checks a translated catalog against its source for placeholder mismatches, broken syntax, truncation risk, terminology drift and untranslated strings. Use before merging translations.
- Translate a software string catalog
Translates a software string file (JSON, PO, XLIFF, ARB, Android or Apple strings) keeping keys, placeholders, plurals and length limits intact. Use when localizing an app's UI text.
- Write ICU plural and select messages
Converts messages with counts, gender or choices into correct ICU MessageFormat for each target locale's plural categories, with test values. Use when strings depend on a number or gender.
- Write translator context notes
Adds translator-facing context to an existing string catalog - where each string appears, length limits, placeholders, tone, plurals, gender and do-not-translate terms - in its own format.
Not: translating prose (translation).