1 / 15

Standardizing the localization process

Standardizing the localization process. Dave Kim. Localization Producer Sony online entertainment. Sony Online Entertainment International Operations and Development (created in 2001) Current Active Localization Projects

hogan
Download Presentation

Standardizing the localization process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Standardizing the localization process Dave Kim Localization Producer Sony online entertainment

  2. Sony Online Entertainment International Operations and Development (created in 2001) Current Active Localization Projects EverQuest II, PlanetSide, Pirates of the Burning Sea, Free Realms, The Agency, DC Universe Online, Legends of Norrath, Free Realms TCG, Match Attax, Station.com Annual Workload Number of Updates: 50~60 updates New English Word Count: ~ 2.0 Million words annually Total Translated Word Count: ~ 8.5 Million words annually Total Word Count in Translation Memory Database Total English Word Count: ~ 15 Million words Total Translated Word Count: ~ 60 Million words Overview

  3. Capability Maturity Model Integration (CMMI) CMM was developed by Software Engineering Institute (SEI), Carnegie Mellon University (CMU)

  4. Localization without Standardization • No Translation Engine • No Persistent Unique IDs • No Standard Translation Data Exchange Format • Ad Hoc Localization • Localization with Standardization • Integrated Translation Engine • English Strings with Persistent and Unique IDs • Streamlined Translation Data Exchange Format • Modern Localization Workflow • Localization with Optimized Standardization • Translation Engine Captures Lookup Calls • Translation Strings with Status • Contextual Data Exchanged • Work Flow Automation with Feedback Evolution of Localization Standardization

  5. Localization without Standardization

  6. Localization without Standardization

  7. INITIAL Localization Process

  8. Maturation • The first step is managing the chaos. You can get quite good at each of these steps in the chain. • Eventually you reach the limits of chaos. • The next step is standardization. • Standardization of process. • Standardization of data. • Standardization of tools. • At SCE standardization is LAMS, at SOE it is C*STAR.

  9. No Translation Engine • No Persistent Unique IDs • Ad Hoc Translation Data Exchange Format • Ad HocLocalization Work Flow Implementing Standardization • Integrated Translation Engine • English Strings with Persistent and Unique IDs • StandardizedTranslation Data Exchange Format • Modern Localization Work Flow

  10. Benefits After Standardization

  11. Benefits After Standardization Outsourced Translation 60% workload Exact Match Translation (70% Disc) New Game Assets Publish (15% Disc) 25% workload Incremental Translation (50% Disc) 15% workload

  12. Optimization • Standardization for each project. • Standardize the data (content and context). XLIFF, Java Properties, XML schemas • Standardize the tools. • Standardize the processes. • The next step is to measure and optimize your standardization. • Create metrics and feedback systems. • Optimize based on those metrics and feedback. • The goal is continuous improvement, in all areas: • Cost reductions. • Quality improvements. • Greater speed and agility.

  13. Integrated Translation Engine • English Strings with Persistent and Unique ID • Streamlined Translation Data Exchange Format • Modern Localization Work Flow Optimizing the Standardization • Translation Engine Captures Lookup Calls • Translation Strings with Status • Contextual Data Exchanged • Work Flow Automation with Feedback

  14. Optimized Standardization

  15. Takeaway • Standardization = Efficiency • 40% of translations internally from tools. • Saving 2+ man years of engineering per MMO. • Turn around 105K words in 10 days, pushing daily with no new builds from engineering. • Optimization = Quality • Proper grammar. • Better translations from fuller context. • Faster, more productive QA.

More Related