Identify menus, dialogue, tutorials, item descriptions, error messages, captions, and text embedded in artwork. Some strings are easy to overlook because they appear only after a failure or unusual action. Keep them in the review plan.
Test the layout with difficult examples
Try longer headings, multi-line labels, large text, and the character sets the project needs. Check reading order and direction where relevant. A translator should have context about where a string appears and any space or tone constraints.
Avoid concatenating fragments in ways that assume one language's grammar. The development approach should support the actual language plan. Voice work can also change timing and may require revised scenes or caption breaks.
Have appropriate language reviewers test the implemented build, not only a spreadsheet of translations. They can find clipped text, incorrect context, pronunciation issues, and mismatched prompts that a document review misses. Record which languages and devices were actually checked. A machine translation can support drafting, but it is not evidence of a natural, audience-ready localized game. Planning these questions early makes later language work more manageable without promising review or language expertise that has not been provided.