5 Localization Problems That’ll Make You Go Crazy

Our team ran into these troubles during L10n of both our database ER-designers for MySQL and PostgreSQL.

We’re digging up some repressed memories and sharing some of the craziest localization problems that will truly make your head spin!

Source: 5 Localization Problems That’ll Make You Go Crazy


I18n thoughts inspired by pain


For those who were born long time ago, in a galaxy far far away, i18n means “Internationalization”.

Every outstanding product (PgMDD is not an exclusion) reaches the specific stage when users demand some drums and whistles beside the main functionality. And one of these issues is notorious “Internationalization” (I keep silence about supporting Linux… my pet peeve). At least for Database Software I’m one hundred percent sure it is so.

Forgive me, French and Germans… Yeah, you guys are the biggest i18n-beggars. Even Asian ninjas are nervously smoking in aside comparing to you. 🙂 I hope, no offense? 😉

Indeed, how can you work with server without knowledge of English? SQL is subset of English, for a minute. Yeah, I heard this shit about national morale. And one more nail in the coffin. Some terms cannot be translated. Or this will be such a crap… Ah, anyway. Where are we?

So I gathered some i18n statistics for PgMDD. If you’re developer you might be interesting in a workload you might face with during i18n. If you’re simple user you will get an idea of how difficult it is (yeah, give old man a hug). All data is collected for English language as a base interface language.

  • Total chars 38073
  • Total chars without spaces 32846
  • Total words 6767
  • Items to translate 2644

Items are control hints, resource strings, window captions, dialogue questions, menu items, button texts etc. Logically indivisible units in other words.

P.S. Don’t do drugs! Make love!