Why Does Game Localization Take So Long?

It’s common to see gamers complaining about the time difference between game releases in different territories – sometimes up to several months. Even if game localization takes much less time than it used to, there are still cases of long delays between local releases.

It is important to understand the game localization process as a whole. Even in this era of dematerialized content (which means less time spent on packaging, manufacturing, etc.), there is not much you can do to speed up the translation/QA testing stages.

Does game translation really take that long?

I have worked on RPGs containing several million source words. However, even an experienced translator won’t be able to handle much more than 3,000 words a day. In some cases, a single translator would need a few years to translate a large RPG on adventure game!

Of course, splitting the work between translators is an obvious solution to reduce that time, but it also creates issues that are time-consuming in themselves: translators have different writing styles, so consistency issues may arise, making the proofreading and linguistic testing process longer.

In all cases, testing takes an awful lot of time: to see the translated strings in context, even with an automated script, you will need to sit in front of a screen for hours and hours. When mistakes are found, developers have to implement the fixes and send the game back to testing, and there is no shortcut here – you can’t have unlimited developers doing this work.

With a well-optimized localization process, developers can get their games ready for new markets in a reasonable time. But for text-rich games, there aren’t too many workarounds, especially if you decide to localize the game after its initial release.

Isn’t there anything we can do about it?

In order to release a game worldwide at the same time, organization is key: you would need to prepare the game texts during the design stage and get the localization team on board as early as possible: ideally translation should start before programming does! Linguistic testing should then be undergone at the same time as functional testing.

The problem, currently, is that localization is overlooked by most developers: in general, texts are prepared in the late stages of developments, when it’s already too late. The best way to go about this is to educate developers about game localization and have them plan localization as early as possible.