Best for
- Products going international for the first time
- Codebases where text lives hardcoded in a thousand places
- Fixing the date/number/currency bugs locales expose
What you give it
- The target languages and regions, and which flows matter first
- Decisions on tone and formality per market when asked
What you get back
- Every user-facing string found, externalised and keyed consistently
- Locale-correct formatting for dates, numbers, currency and plurals
- A report of the layouts and flows that will break in longer or right-to-left languages
How it works
- Sweeps the codebase for user-facing text, including the sneaky places: errors, emails, validation messages, titles.
- Externalises strings with a consistent key scheme, preserving meaning with context notes for translators.
- Replaces hand-rolled formatting with locale-aware date, number, currency and plural handling.
- Audits layouts for expansion, truncation and direction problems.
- Sets up the translation workflow so new strings cannot silently ship hardcoded.
Example
You: We are launching in Germany and Japan. Get the product ready.
Result: 412 hardcoded strings externalised with a consistent key scheme, plural rules fixed in eight places that assumed English, date and currency formatting moved to locale-aware formatters, and a layout report naming the five screens German text will overflow.
Limits — please read
- It prepares the mechanics; actual translation needs translators (it structures their work).
- Legal and cultural adaptation per market is flagged, not decided.
- Right-to-left support is structural work — it reports the real size honestly.