Localization Summit 1

Localization Tools Andrea Ballista, Binari Sonori A Panel Moderator: Miguel Á. Bernal-Merino, Roehampton University Panellists: Andrea Ballista, Binari Sonori Jennifer McKearney, Bioware Stephanie O'Malley Deming, Xloc Ben Wibberley, Babel

Localization tools Why? Worldwide simship releases are the standard now. Gone are the days when titles in Europe were published 2 weeks to 3 months later than in the US. The industry is looking for more efficient processes to have great quality multilingual contents, ready for integration and testing, at the same time. This new global scenario pushes for defining enhanced collaboration systems and asset sharing models among the overall international production chain. Tools can help to implement the optimized process and make life easier in targeting succesful localizations.

Localization tools What? Today we’ll offer you a snapshot of the major categories of tools type, scope and features from multiple perspectives and their relationship with the evolution of the international localization processes. Content Extraction & Integration tools. Project managing tools. Translation tools. Bug reporting tools.

Content Extraction & Integration tools features: Facilitate the building of the most updated snapshot of the source data. Maintain structure and consistency with previous source data extractions. Maintain full accessibility to the complete set of source data. Preserve at best all the data related context information. Facilitate an easy and secure localized content integration for multiple languages.

Project managing tools features: Facilitate an integrated schedule and planning approach for the international localization process. Help defining a complete localization status control panel. Identify a clear source & target asset repository. Include user profiling facilities. Facilitate asset accessibility to all the profiled users. Facilitate users collaboration on relevant topics. Include tracking tools (history).

Translation tools features: Be able to import / export in multiple formats (e.g. XML format). Re-use at best previously translated material. Offer terminology support (content glossaries and naming conventions). Work at best with the available reference context extracted with the source assets. Link directly with relevant MM resources. Offer accurate word counts.

Bug reporting tools features: Facilitate a quick and clear bug input process. Clearly define bugs leverage. Facilitate the game asset cross reference. Enhance the effective cooperation between the testing team, the development team, the international content fixing loc team. Facilitate overall bug status, analysis and recovery policy, regression cycle to final master. Keep a history of previous builds and assets.

Open questions Are “standard formats” useful for the process and for the tools? Is a shared knowledge on shared practice useful to smooth the process (activity, resource and timing)? Are tools useful to “sync” the development team and international team communities? What problems tool are not able to solve? “Customization” Vs “Standardization”