The Black Box of Video Game Translation Tests — How to Crack it Open (With a 12-Point Checklist)

Translation tests stand as the main gateway to jobs in the video game localization industry. However, with fierce competition and sometimes subjective criteria, they can be a source of frustration for many language professionals.

In this month’s WonderLoc edition, you’ll discover reviewers’ primary criteria for assessing translation tests, even when no scorecards exist. Then, you’ll get your hands on a proofreading checklist to seriously make your tests more polished.

Ready? Let’s get cracking!

Translation Tests Criteria

Most translation tests have a scoring system following a handful of criteria. Let’s take a look at the most common categories and their respective evaluation points. Bear in mind that specific names can vary across translation companies and game studios. Also, some tests lack formal criteria and are assessed holistically, with only an overall score or Pass and Fail labels. Still, any identified translation mistake will fall into one of the groups below.

• Accuracy evaluates whether the source text is properly rendered in the target text. Reviewers will check for semantic distortions, mistranslations, and untranslated content. These mistakes usually result from over-tweaking sentences until they sound ‘natural.’ When proofreading your test, always check your translation against the source to ensure it doesn’t miss key information or distort it.
• Style relates to the content type of a test’s activity. Consider the following examples. A store page needs to capture readers’ attention and persuade them to download or purchase the game. User guides have clear descriptions and instructions. Dialogue text must flow well and captivate gamers. Make sure you adjust your translation choices for each.
• Terminology means maintaining consistency on two fronts: industry-standard translations (cooldown, ranged attack, etc.) and the terms you translated within the test. For the first group, look up reputable game glossaries in your language pair. If you can’t find them, research critically acclaimed localizations in your language and their translation solutions. For the second group, make sure recurrent names, game mechanics, buttons, and interface sections are translated identically across the test.
• The Grammar category assesses how well your translation adheres to standard grammar rules in the target language. Every language has its own set of rules, so be sure to consider broad topics like subject-verb agreement, gender and number agreement, punctuation, verb conjugation, case declensions, and word order. Remember, grammar can be more flexible in certain content types, so adapt your approach accordingly.
• Formatting in the target text must closely follow the source material. This includes line breaks, HTML codes, and variables. Some test activities set character limits for translations, also evaluated under Formatting.

Translation Test Checklist

Translating your test is just the first step. Next, you want to review it carefully, putting yourself in the reviewer’s shoes. Remember, tests are fiercely competitive, so evaluators will look for small details to dock points from candidates until one stands out.

Use the checklist below to identify slip-ups that could harm your score.

1. Have I justified arguable translation choices in the comments? Are all my comments clear, concise, and strictly necessary?
2. Do my punctuation, capitalization, and time format choices follow either the source text or a recognized style guide in my native language? Have I made that choice clear to the reviewer?
3. Have I run a spellcheck to remove typos and misspellings?
4. Have I researched grammar books to double-check points I’m not 100% sure about?
5. Do the tone, style, and register in my translation match the source text’s?
6. Are all tags, codes, and variables well-formed against the source?
7. Have I made my sentences gender-neutral when addressing the player or a character of unknown gender?
8. Do my sentences concatenate well with placeholders? E.g., in {0} unlocked, the placeholder could be either a singular, plural, masculine, or feminine noun, so the translation of unlocked should account for that.
9. Have I adhered to all character constraints, where applicable?
10. Have I maintained consistency within the test for game-specific terms (characters, locations, skills, spells, items, game notions, etc.)? **
11. Do my translation choices follow consolidated game terminology in my native language?
12. Do my translation choices adhere to official platform-specific terminology (D-Pad, Right Stick, Left Bumper, etc.)?

Failing a translation test doesn’t mean you’re unfit for the job. Often, a failure just means someone scored higher under very specific circumstances. Try to identify what went wrong, ask for feedback when possible, and improve on those points for your next attempt.

Don’t forget that the freelance market is ever-changing. A company might be well supplied with translators from your language pair at a given time, only to need a couple more six months later. Keep a record of agencies and studios that turned you down, and come back stronger once enough time has passed.

—

Let me hear from you!

Are there any criteria missing from my list?

Which additional steps do you take to polish your translation tests?