Continuous localization of mobile and multiplayer games
When it comes to localizing “traditional” games, where the content is finalized and requires no further updates (or minor updates at large intervals), there is a clear process that corresponds to the procedure outlined on our website. In most cases, this applies to offline single-player games.
It’s a different story when it comes to various mobile projects, MMO, MOBA and other multiplayer games. These kinds of games are constantly updated, with developers adding content (promotions, updates, holiday-related challenges, new characters, chapters, locations, etc.) to be localized into the languages they need.
times a week With some projects, that is how often new content arrives to be localized. The process built for a finished game does not survive that pace.
Our goal is to keep pace with developers and deliver high-quality localized content whenever it’s required. While there are generally no issues with the speed of localization (updates contain small sections of text, not several thousand words), ensuring high quality requires devoting attention to the particular features of continuous localization.
Both localization specialists and developers/publishers can avoid errors and provide high quality and consistency of the text by following several simple rules:
1. Assign special localization teams to long-running projects
If one of your teams translated and proofread the main in-game texts, the same team should work on the Christmas update for the game a year later. They know the setting, context, specifics and mechanics. They know how locations and characters look. And, most importantly, they know how these elements have been translated before.
2. Maintain and constantly update glossaries and translation memories
There are various reasons why it may not be possible to follow the previous rule: translators can get sick, retire or be unavailable in the moment. In this case, glossaries and translation memories help to integrate other people into the project without harming quality or speed.
Lists of in-game terms (names of characters, locations, objects, etc.) and their recommended translations.
A database containing a set of previously translated text segments. Updates often contain previously used pieces of text, albeit slightly altered.
A translator working with a glossary will know not to turn “Blackwind Castle” into either of these.
Even if another person translates the update, he/she can review suggested translations from the translation memory.
Both translation memories and glossaries can be easily maintained with specialized CAT tools. The most popular ones are:
Updated translation memories and glossaries should always be available to both localization specialists and developers/publishers.
3. Spot testing
To ensure the highest localization quality, do not forget about linguistic testing. But what if you need to check only a small amount of text from the latest update? Obviously, re-testing the full game again is too expensive and takes too long.
The best solution is spot testing for updates, where a translator can use in-game cheats to quickly find the required game fragment. Where this is not possible, any methods to cut out the “unnecessary” part of the content will suffice:
- Gameplay videos
- ScreenshotsIn minor updates.
- Game builds that start right in the new location
Nothing guarantees the complete absence of localization mistakes. But following these three simple rules can significantly reduce the risk.
Shipping updates every week?
Tell us how often your content changes and which languages you need. We will fit the process around your release schedule.