This document discusses the importance of software localization and an agile localization process. It provides the following key points: - Survey results found that 70% of respondents saw positive impacts of localization on customer experience and market share. Localizing apps increased download volumes by 128% and revenues by 26% on average. - An agile localization process involves preparing materials, building translations, integrating them, finalizing, and deploying. It requires choosing file formats and directory structures translators can work with comfortably and technologies that allow extraction, building translation files, and combining them. - Continuous translation from a system translators are familiar with and automation are important to successfully integrate translations into the development process and app builds.

1. Why is Localization Important?
Matt Jackowski @mjjacko

2. Why is Software Localization Important?
‣ Overall, 70 percent of respondents indicated a positive impact of
localization in terms of customer experience and market share
regardless of industry, company size and the stage of localization
maturity.
- The Transifex State of Localization Benchmark Survey - 2014
Matt Jackowski @mjjacko

3. Why is Software Localization Important?
‣ On average, apps that introduced a native language version
increased their download volumes by more than 128% in the week
following the update. Average revenues over the same period
increased by roughly 26%. East Asian countries were the most
impacted by the translation: China and Japan experienced the
highest improvements in total downloads, and China and South
Korea saw the biggest jump in revenues.
- Distimo report, The Implication of App Translations - 2012
Matt Jackowski @mjjacko

4. Agile Localization Process
Matt Jackowski @mjjacko
Prepare
i18n (Engineering)
Style guide (Linguistic)
Glossary (Linguistic)
Build
Coding (Engineering)
Translation (Linguistic)
TM (Linguistic)
Integrate
Continuous Translation
(Engineering)
Build Translation Files
(Engineering)
Finalize
Testing (Engineering)
Review (Linguistic)
Deploy

5. Prepare
i18n (Engineering)
Style guide (Linguistic)
Glossary (Linguistic)
Build
Coding (Engineering)
Translation (Linguistic)
TM (Linguistic)
Integrate
Continuous Translation
(Engineering)
Build Translation Files
(Engineering)
Finalize
Testing (Engineering)
Review (Linguistic)
Deploy
Matt Jackowski @mjjacko
Agile Localization Process

6. i18n options for Javascript
Matt Jackowski @mjjacko

7. Prepare
i18n (Engineering)
Style guide (Linguistic)
Glossary (Linguistic)
Build
Coding (Engineering)
Translation (Linguistic)
TM (Linguistic)
Integrate
Continuous Translation
(Engineering)
Build Translation Files
(Engineering)
Finalize
Testing (Engineering)
Review (Linguistic)
Deploy
Matt Jackowski @mjjacko
Agile Localization Process

8. Build and Integrate - Part One
‣ File Format: Expecting translators to work within the
JSON structures that many libraries use is just not
reasonable. We need to be able to keep translations in
‘translator friendly’ formats.
‣ Directory Organization: Large projects can contain many
strings and keeping them organized is a key to any
localization project.
Key parts to the Localization Build process:
Matt Jackowski @mjjacko

9. Prepare
i18n (Engineering)
Style guide (Linguistic)
Glossary (Linguistic)
Build
Coding (Engineering)
Translation (Linguistic)
TM (Linguistic)
Integrate
Continuous Translation
(Engineering)
Build Translation Files
(Engineering)
Finalize
Testing (Engineering)
Review (Linguistic)
Deploy
Matt Jackowski @mjjacko
Agile Localization Process

10. Build and Integrate - Part Deux
‣ Continuous Translation: Translations should come from a
system the translators are comfortable with which should
integrate with our app build structure. Much like our
approach to writing code, we will merge in translations during
out development process.
‣ Automation: Automation is a cornerstone of the localization
process. To be successful we need to choose technologies
that allow us to extract from source, build translation files,
and then combine together as part of our i18n framework. If
any one of those step is manual, all bets are off.
Key parts to the Localization Integration process:
Matt Jackowski @mjjacko

11. An Effective Localization Process
Demo of ‘Build and Integrate’ Steps
Matt Jackowski @mjjacko
Prepare
Build
Integrate
Finalize

12. Thank you!!
Matthew Jackowski
@mjjacko
Integration Engineer
Matt Jackowski @mjjacko

13. One more thing…
Transifex is a continuous localization platform powering the process of launching products into
multiple languages for companies with rapid development cycles.
Transifex’s mission is to connect people around the world and to enable anyone, anywhere to
enjoy content in their native language.
Do you want to learn more?
Matt Jackowski @mjjacko