Some localization bugs are not caused by the translation at all. The text is right and the interface still looks broken, because the interface was built around Latin script and English length. Here are four that tend to appear only when you ship Chinese, Japanese, Korean or Arabic, with a quick way to catch each.

1. Font fallback that mixes typefaces

If your UI font does not include a script, the browser quietly falls back to another font. The result is mismatched weight, uneven spacing and lines of text that look like they came from different products. Chinese, Japanese and Korean text also need adjusted line height, and Arabic needs a font whose shaping works with the rendering engine.

Declare the language, and give each script a deliberate font stack:

<html lang="ja"> 
:lang(ja) { font-family: "Noto Sans JP", "Hiragino Sans", sans-serif; line-height: 1.7; } :lang(ar) { font-family: "Noto Naskh Arabic", "Amiri", serif; } 

Full Japanese web fonts can weigh several megabytes, so subset them and load only what a page needs. Check that your pipeline is Unicode end to end: if any step is not, you will see boxes, question marks or garbled symbols.

2. Mixed-direction strings

In right-to-left languages, a label that mixes Arabic with numbers, Latin product names or variables can display in an unexpected order. The usual culprit is a dynamic value inserted into a right-to-left sentence. Isolate it:

<p dir="rtl">الطلب رقم <bdi>#A-1042</bdi> تم تأكيده</p> 

<bdi> (or dir="auto" on the element holding the value) stops the surrounding direction from reordering the inserted text. Beyond that, mirror the layout with logical CSS properties (margin-inline-start, padding-inline-end) and flip icons that imply direction, such as arrows and progress indicators.

3. Layouts that cope with long text but not short text

Developers test for expansion, because German can run about a third longer than English. Fewer test for contraction. Chinese and Japanese often use fewer characters, but each is visually dense. A button that said "Submit Order Now" in 18 characters becomes 6 characters in Japanese. Without a minimum size, the button shrinks to a poor touch target, and fixed-height banners can clip complex characters.

.btn { min-inline-size: 7rem; min-block-size: 44px; } .card-title { line-height: 1.5; /* no fixed height that clips tall glyphs */ } 

Use pseudo-localization with both longer and shorter strings so truncation and shrinking show up before translators are involved.

4. Short labels with no context

A button that says "Close" could close a window, end a session or dismiss a notification. In French, "fin" can mean end, finish or goal. A translator who only sees the key and the string has to guess. Give every string a description and, ideally, a screenshot:

{ "dialog.close": { "message": "Close", "description": "Button in a modal: dismiss this dialog without saving" } } 

Keep keys stable so translation memory keeps working, and avoid building sentences by concatenating fragments, since translators cannot reorder them.

A short pre-release routine

  1. Run a build with pseudo-locales (long, short and accented).
  2. Switch the layout to right-to-left and look for flipped icons and reordered mixed text.
  3. Check each script on real devices, not only in a desktop browser.
  4. Review in context in staging with a native speaker.

If you want the first post in this series, it covers five i18n bugs we keep finding in real projects. Corrections and war stories are welcome in the comments.