Most localization problems are not translation problems. They are engineering problems that only become visible once a second language shows up. Here are five bugs that keep appearing in real projects, with a way to catch each one before release.
1. Strings glued together in code
// Looks harmless const msg = "You have " + count + " new " + (count === 1 ? "message" : "messages"); Word order, plural rules and grammatical gender differ by language, so concatenation cannot be translated. Use a message format that carries the whole sentence and the plural rules:
{ "inbox.new": "{count, plural, one {You have # new message} other {You have # new messages}}" } Languages such as Arabic and Polish have more plural categories than English, so the format must allow them.
2. Layouts that assume English length
German and Finnish strings are often much longer than English ones. A fixed-width button that fits "Submit" will clip a longer equivalent.
How to catch it: use pseudo-localization in development. Replace every string with a longer, accented version such as [Ŝûbmîţţţ] so truncation, hardcoded widths and missing glyphs show up immediately, before any translator is involved.
3. Hardcoded formats
Dates, numbers and currencies are formatted differently around the world. 1,250.50 is 1.250,50 in much of Europe, and 03/04/2026 is ambiguous without a locale.
new Intl.NumberFormat("de-DE", { style: "currency", currency: "EUR" }).format(1250.5); // "1.250,50 €" Use the platform's locale APIs rather than string manipulation, and store dates in an unambiguous format such as ISO 8601.
4. Right-to-left as an afterthought
Arabic and Hebrew need more than text direction. Layout, icons that imply direction and mixed-direction text all behave differently. Prefer logical CSS properties over left and right:
.card { margin-inline-start: 1rem; padding-inline-end: 0.5rem; } Then test with real RTL content, not just a flipped screenshot.
5. Strings without context
A translator who sees only "Book" cannot know whether it is a noun or a verb. Add a short description or screenshot to every key, and keep keys stable so translation memory keeps working.
{ "reservation.cta": { "message": "Book", "description": "Button label: reserve a table" } } A quick checklist
- No concatenated sentences
- Plural-aware message format
- Pseudo-localization in CI
- Locale APIs for dates, numbers and currencies
- Logical CSS properties
- Context for every key
About this series
We are a localization team and we will keep writing short, practical posts like this one about the engineering side of shipping in many languages. Comments and corrections are welcome.