Tip: Provide ample room in the design between the different elements.
Strategic Foundation: Before diving into the video game localization process, developers must select target markets based on cost, competition, and revenue potential, then identify what needs adapting. Addressing technical requirements early – like internationalized code and UI flexibility – prevents costly setbacks.
Building a Localization Kit
Once you’ve selected markets for localization and accounted for all of the above, make this information accessible to your localization team via a localization kit (or LocKit). If you haven’t found the ideal team to localize your game just yet, we’ve outlined the criteria to keep an eye out for in our game localization definitive guide.
A LocKit is an all-in-one localization guide for your team in which you provide instructions, files and specifications about the project as a whole.
The benefits of preparing a LocKit include:
● It ensures the smooth communication between teams.
● It accelerates project speed delivery.
● It saves you both time and money.
● It significantly reduces localization challenges from arising later on.
How to build a LocKit
Here’s everything you need to include inside and tips for making the most out of your LocKit to take advantage of its benefits:
● A language list. It goes without saying that you must specify the languages for localization, alongside the region and dialects spoken in that region. For example, if you’re translating your game into Spanish, don’t forget to mention whether your target demographic resides in the US, Spain, or Mexico.
● Files with what needs translation. After extracting your strings from the code, move any text that will be localized inside a stand-alone file such as on Excel (other file types, such as DOC, JSON, are okay too). Additionally, include the voice-over files, if any. Use a separate tab for different types of texts (e.g., dialogues, tutorials), set out any dialogue in the order it is spoken (otherwise the translators will struggle making sense out of the dialogue) and provide as much context as you can via screenshots and comments. Also specify what shouldn’t be translated.
● Previous game translations. If you’ve localized your game before and want your team to adhere to similar or the exact same stylistic standards, you should include older game translations in your LocKit. In case you were dissatisfied with the quality of your older translations, your team can also assess what might have previously gone wrong and address the issue.
● Style guide brief. If there are no game translations available, it’s recommended to include a style guide. Depending on your audience and your brand’s tone of voice, a different style of communication is required. Specifying all spelling, grammar and punctuation rules you’d like your localization team to follow in the LocKit is crucial. This tool is particularly useful to include if your game is text-heavy, such as a story-driven game.
● Glossary. A glossary acts as a dictionary for words and phrases that show up multiple times in the game (such as character names, as we’ve specified above). If you’re localizing a game sequel specifically, it’s expected to include previously translated terms inside the glossary.
Glossaries are crucial, since they can enhance the consistency of all game-translated content. For example, the term “semi-automatic” should be consistently translated as such and never as “handgun”. Otherwise you’d risk interfering with the gamers’ experience. A translation memory tool can help with maintaining a high level of consistency throughout the game.
● Information about the software. You should provide intel about your software’s platform, manufacturer, version, and purpose. That way, the project manager can have any questions answered before the localization process can begin.
Key Resource: A localization kit (LocKit) consolidates everything your game localization team needs – target languages, translatable files, style guides, glossaries, and software details. A well-prepared LocKit streamlines communication, speeds up delivery, and helps maintain consistency across all translated content.
The Actual Localization
The actual localization process will look different depending on the game you’re localizing, but generally, it can be divided into the following stages:
1. Developing familiarity with the game
Before your localization team can dive into the translation, they need to understand what makes your game unique. They might need to play through your game to familiarize themselves with the plotline, characters, and of course, the game’s language. If your game is part of a larger game sequence, the localizers can play through the prequels as well. You might need to allow plenty of time for the team to go through your game, especially if it’s too large in size or has multiple locations to explore.
Tip: Ask your team to provide you with reports about the playthrough progress on a daily or weekly basis.
2. Translating the content
The actual translation process can begin after all strings and content have be transferred to a translation management system. With access to a LocKit, and particularly with the aid of the style guide and glossary, your team can translate your game content with consistency. Access to a translation memory will substantially expediate the process, since it streamlines the translation of any terms, such as character names, that show up with great frequency.
During the same phase, a second pair of eyes, like an editor or proofreader, can cross-check the consistency of the translation. Although you’ll need multiple game translators, one editor will do. Just keep in mind that translating the voiced portions of the game might take significantly longer than the translation of the user interface sections.
Tip: Give the localization team the opportunity to see the final translation on screen, so they can make any needed changes before the quality assurance phase.
3. Recording voice over
When the voiced sections have been translated properly, that is with utmost consistency and accuracy, only then should you start the game voice over recordings. You might have to mark lines from the script to indicate whether they should be time-synched (when the dialogue matches the action scenes) or lip-synched (when the dialogue matches the speaker’s lips).
Additionally, it’s important to provide your localization team with pictures and descriptions of the characters (i.e., mention age, gender, voice type, background, etc.), as well as sample voice files. This way, you can ensure your game localization partner hires the best-fitting voice actors for each specific role.
Tip: To get an accurate quotation estimate, provide a detailed description about the audio, mentioning the number of voice actors, line and word counts, and maximum time per line.