This document discusses localization processes and tools. It covers the localization of in-game assets, non-in-game assets, web content, apps, and collateral materials. It describes typical localization workflows and the roles of regional teams, external vendors, and quality assurance. It also outlines key features of localization tools, including import/export functions, translation status tracking, and context windows. Finally, it provides a sample localization quality assurance test flow.

1. Process, Tool,
Localization, Successful
Julie Song

2. 1. In-game localization assets
I. Texts: all of strings displays in-game
II. Artwork texts: graphical images embedded into game, patch logo
III. Map: text on the map with graphic tool
IV. Voice-overs: Script translation, Audio vendor Arrangements, Voice
actor selection, Direct audio recording
V. Cinematics and videos: voice-overs or subtitling
VI. Font: fitting fonts selection, working with professional font
production vendors to newly develop
2. Non-in-game Assets
I. Patch notes
II. Downloader, Installer, Launcher strings
III. Manuals
General In-game Localization Work Scope

3. 3. Web localization
I. Official sites, Cooperate sites, Game related web service
4. App localization
I. Mobile client for both iOS and Android
II. Mobile serviced apps
III. Mobile web
5. Collateral Materials
I. Public Relations: Press release materials review to maintain glossaries
consistency
II. Marketing: Event / Promotional sites or materials trancreation and review
III. External Affair
I. Provide In-game materials to handle potential rating Issue
II. Support Legal & TOU & EULA translation
General Collateral Materials Localization Work Scope

4. HQ Regional Team External Vendor
Minor Fix
Translate/
Review
Export Build Test
Loc QA
Editing
Update
Translate
For Review
Not
Translated
Final Build
Check
Import
Prepare Assets
Proof-
reading
Hand-off
Hand-back
General In-game Localization Work Flow
QA
• Export/Import strings
• Get answers for having
context from
developers
• Handle main schedule
in line with
development
• Assign strings to internal
and external localization
staffs
• Maintain glossary
consistency for the
respective language
• Review and edit the
strings
Localization
• Test localized strings
and text with proper
context using test build
• Propose alternative
solution to improve
localized quality
Loc Producer Vendor
• Translate a bulk of
strings that handed off
from the client
• Handle Propose
alternative solution to
improve localized
strings

5. General Web Localization Work Flow
HQ Regional Team External Vendor
QA
• Export/Import strings
• Get answers for having
context from
developers
• Handle main schedule
in line with
development
• Assign strings to internal
and external localization
staffs
• Maintain glossary
consistency for the
respective language
• Review & edit the strings
Localization
• Test localized strings
and text with proper
context using test build
• Propose alternative
solution to improve
localized quality
Loc Producer Vendor
• Translate a bulk of
strings that handed off
from the client
• Handle Propose
alternative solution to
improve localized
strings
Translate/
Review
Export Staging Test
Loc QA
Editing
Update
Translate
For Review
Not
Translated
Production
Check
Import
Prepare Assets
Proof-
reading
Hand-off
Hand-back
Minor Fix

6. Assign
Final Check
Project
Management
Tool
Export
Translate
Loc
Manager
Loc
Engineer
ReviewFinal Delivery
Translate/
Review
Prepare Assets
General Collateral Materials Localization Work Flow
HQ Regional Localization External Vendor
Test
Hand-off
Hand-back
QA
• Export/Import strings
• Get answers for having
context from
developers
• Handle main schedule
• Assign strings to
internal and external
localization staffs
• Maintain glossary
consistency for the
respective language
Localization
• Test localized strings
and text with proper
context
• Propose alternative
solution to improve
localized strings
Loc Producer Vendor
• Translate a bulk of
strings that handed off
from the client
• Handle Propose
alternative solution to
improve localized
strings

7. Minor Fix
Translate/
Review
Export Build Test
Loc QA
Editing
Update
Translate
For Review
Not
Translated
Final Build
Check
Import
Prepare Assets
Proof-
reading
Hand-off
Hand-back
Features for In-game Localization in Localization Tool
• TRANSLATION
WINDOWS
• GLOSSARY /TOKEN
CHECK
• IMPORT/EXPORT
• TRANSLATION
STATUS
• PROJECTTREE
• COMPARE / FILTER
STRINGS
• CLAIM/ASSIGN
STRINGS
• FIND/REPLACE
• TRANSLATION MAMORY
• PROJECT STATISTICS
• CONTEXT
WINDOWS
• TEST BUILD
• LANGUAGE
PACK
GENERATOR

8. • ProjectTree: Must to run project file
between versions
• Import/Export: Essentially CSV, EXCEL,
TXT format
• Translation Status: Differentiate each
string’s translation status such as Not
Translated,Translated, For Review,
Complete, Auto translated, Best Guess
KEY FEATURES FOR LOCALIZATION TOOL

9. • Compare / filter strings:
Compare strings from
version to version
• Claim/Assign strings:
Translator claims their
own strings / Lead or
Producer assigns certain
amount of strings to
translators
• Find/Replace strings:
Used for revision and edit
KEY FEATURES FOR LOCALIZATION TOOL

10. • Translation Window: Use to enter
translation. It contains flags, context,
translation status, original and garget
language columns.
• Glossary /Token Checker: Maintain specific
key words for the project or general terms.
Token (placeholder) should be secured to
run a build for both in-game and web
KEY FEATURES FOR LOCALIZATION TOOL

11. • Context Windows: Grab a
hint to a string for translator.
Usually a comment from
developers.
• Translation
Memory(Engines): It is a
service that can automatically
translate text from one
language to another
languages. Contains back-up
data of the internal
translation memory for each
project.
KEY FEATURES FOR LOCALIZATION TOOL

12. • Project Statistics: How far a certain project are going. Displays a
volume of remained translation, review, complete strings
filtering weekly, monthly, daily.
• Test Build & Languages Pack Generator:Tool supports several
operations systems, compilers, file formats and data storages.
(Flash, .net, Android, HTML, iOS, Java, xml). Runs an own
language pack into the test build so Localization team can
conduct LQA properly.
KEY FEATURES FOR LOCALIZATION TOOL

13. SAMPLE: WorldServer

14. SAMPLE: Sisulizer
ProjectTree
Translation Statistics
Context Window Original Source Target Language
Translation Status

15. WHAT YOU NEED TO CHECK
Build Role & Responsibility Refine your localization
workflow globally
Examine tool development
teams resource to operate
Redefine game
localization quality

16. Appendix: Localization QA Test Flow
Tester Finds an issue
Tester researches the issue
in Bug Tracking Tool
Tester researches steps for reproduction
and writes the bug
The Devs implement a fix and change the bug
status to Implemented
Bug appears to be fixed and is moved
to Verified
Bug is tested again in a new build
Bug is considered Fixed and
will probably not be tested
again
Tester continues testing
Issue is already reported
Issue has not been reported
Bug is approved as a valid issue and sent to design to fix
Issue is marked Duplicate, Won’t Fix, or
Not A Bug in Bug Tracking Tool
Bug is reproduced successfully and is moved
back to Active
Game Test Flow