Localizing Large RPGs

2. Localizing Large RPGs • Ryan Warden • Localization Project Manager (Mass Effect Franchise), BioWare • Chris Christou • Lead Localization Tools Programmer, BioWare

3. BioWare

4. By the numbers • Mass Effect: • 300,000 words • 25,000 lines of VO • Mass Effect 2: • 450,000 words • 30,000 lines of VO • Localized ME2: • 2.7 million words • 140,000 lines of VO • 300+ days in studio, 350+ actors

5. Video game localization

6. Preparation • Compile a localization kit: • Pronunciation guide • IP Glossary • Translator Q&A documents • Character Bible

7. Character Bible

8. Text is ready for loc • Created huge, granular schedule • This doesn’t work • Too much churn during dev • What does work? • Following EN VO recording

9. Our localization cycle

10. What needs localization? • Determined by major/minor string edits • Major edit – requires translation • Minor edit – does not require translation

11. Standardized tools

12. Exports vs. Imports • Export: we send strings for translation • Imports: we receive translated strings and place them in the database

13. Our translation pipeline

14. Modified pipeline:no intermediate management system

15. String history timeline

16. String history timeline • String does not require translation • String does require translation

17. Statistics • How much text requires translation & Re-translation?

18. Exports • Non-conversation strings • Too disparate to make sense; need to provide context • Group like strings together in “string types” • Export by string type

19. String Types • Achievements • Art placeables • Character names • 360 GUI • PC GUI • Credits • Error messages • Galaxy Map • Loading hints • Quest title, description

20. Conversation structure

21. Conversation Previewer

22. Conversation meta-data • Who’s speaking? • Who’s listening? • Are there any time restrictions for the lines?

23. Data medium • XML • Allows us to cleanly define associative data • Avoids proprietary file formats • Fast to create, fast to process • Facilitates cross-project apps

24. Imports • Use same XML structure as exported documents • XML is processed and validated • Ensure that imported strings will not break the game • Automated checks to avoid bad data • Can identify process gaps

25. Types of validation checks • Non-critical • Warning-based • Blank/non-existent translations • Critical • Error-based • Multiple translations for a single uniquely-identified string

26. Loc VO recording • Same-day turnaround for loc recording scripts • EN reference audio provided with scripts • VO Scripts

27. Locking down content • When can content be considered locked? • When the game is on the shelf

28. Data compartmentalization • Create another release candidate • Separate main game from DLC • Create patch content • Etc .

29. Compartmentalize by module • Use different modules for data • Control read/write access for each module • Safely create different amounts of content

30. Localization testing • Try to front-load risk • Jenga model • Spell-check • Web reports • Out-of-game testing

31. Same process, different projects

32. Q&A • Questions? Comments? • Ryan Warden – ryanw@bioware.com • Chris Christou – christou@bioware.com