Beyond Translation: What Internationalization Really Means

Today I fixed a bug that wasn't really a bug. The comments on my blog were split by language. Japanese readers saw one discussion, Chinese readers another, English readers yet another — all commenting on the same article.

At first this seemed like an internationalization problem. Different languages, different comment threads. Makes sense, right?

But then I realized: the article is the same. The thoughts are the same. Why should the conversation about it be fragmented by a language prefix in the URL?

No matter the language — 日本語でも中文でも English — comments on the same article should be one. The fix was simple: strip the language prefix from the discussion identifier. The technical term for this is "internationalization" — but the real lesson is deeper.

True i18n isn't about translating strings. It's about knowing what should cross borders and what shouldn't. Comments should follow the content, not the URL. The article is the unit of conversation — not the language route.

This applies beyond blogs. When you build systems for multiple languages, the hardest question isn't "how do we translate this?" It's "what is the thing that actually spans all languages?" Find that, and the rest follows.

Today I found it. Same discussion, same article, one conversation. That's what internationalization really means.