localization toolkit 3.0 gary lefman, cisco systems martin guttinger, cisco systems
TRANSCRIPT
Localization Toolkit 3.0
Gary Lefman, Cisco SystemsMartin Guttinger, Cisco Systems
Speakers
• Martin Guttinger: Manager, VTG Localization, Cisco Systems
• Gary Lefman: Software Engineer, VTG Localization, Cisco System (via video & conference bridge);
Agenda• A brief overview of the team• Why a toolkit in the first place?• Toolkit (R)evolution – 1.0 vs. 2.0 vs. 3.0• Toolkit Architecture & Workflow• Challenges of building a Toolkit• Challenges of Using a toolkit• Toolkit demo• What is next – Localization Toolkit 4.0
A Brief Overview Of The Team• Specialized in Unified Communications Localization• In business for over ten years, 10 employees, serving
3 divisions• 20 products in up to 35 languages• Core Languages localized for every product and
release• Non-core only localized if previously supported or if
paid for by the theatres through field-funded localization process
Core LanguagesWritten Language Spoken Dialects
English (U.S.) U.S., U.K., Australian
Simplified Chinese (PRC) Mandarin (PRC, Taiwan)
Traditional Chinese (Taiwan, Hong Kong) Cantonese (Hong Kong)
Japanese Japanese
Korean Korean
German German
French (France) Parisian
Italian Italian
Spanish (Spain) Castilian, Colombian
Portuguese (Brazil) Brazilian
Arabic Saudi Arabia
Dutch (Netherlands) Dutch
Swedish Swedish
Russian Russian
Danish Danish
Why A Toolkit In The First Place?• 15 core languages, but…• Demand for new languages never stops, but current
economic environment means flat budgets and headcount
• Helps to increase revenue/bookings• Helps to prevent bad business decisions• Field-funded localization process is expensive and does
not scale• Toolkit pushes control and responsibility to the field
(fiscal & tactical)
Potential LanguagesIP Phones Rich Media Uni. Messaging Contact CentrePortuguese(Portugal) Portuguese(Portugal) Portuguese(Portugal) Portuguese(Portugal)
Greek(Greece) Greek(Greece) Greek(Greece) Greek(Greece)
Catalan(Spain) Catalan(Spain) Catalan(Spain) Catalan(Spain)
Norwegian(Norway) Hebrew(Israel) Hebrew(Israel) Norwegian(Norway)
Finish(Finland) Dutch(Belgium) Norwegian(Norway) Finish(Finland)
Hebrew(Israel) Galician(Spain) German(Switzerland) Hebrew(Israel)
Dutch(Belgium) French(Belgium) Finish(Finland) German(Switzerland)
Galician(Spain) German(Switzerland) Dutch(Belgium) Dutch(Belgium)
German(Switzerland) Norwegian(Norway) Galician(Spain) French(Belgium)
French(Belgium) Finish(Finland) French(Belgium) French(Switzerland)
Basque(Spain) Basque(Spain) French(Switzerland) Basque(Spain)
French(Switzerland) French(Switzerland) Basque(Spain) Hungarian(Austria)
... ... ... ...
*Highlighted : already localised (or no need)Core Languages will be available also in the final list
EMEA
What Is Cisco’s Toolkit Vision?
• Application that automates the process• Easy, intuitive interface & documentation• Framework with product plug-ins.• Integrates with Translation technology (TMS, Passolo)• Can be used by non-technical user• Provides a “controlled localization environment”
(Brand Protection, Quality assurance)• Hides the complexity of localisation.
Toolkit (R)evolution – 1.0 vs. 2.0 vs. 3.0
• Localization Toolkit 1.0 – Zip file• Localization Toolkit 2.0 – Zip file + Word Doc• Localization Toolkit 3.0 – Application
– Client-Server application – it is a piece of software– Wizard that walks user through the localization process– Easy to use – tailored to non-technical users– Integrates with state-of-the-art translation technology– Offers a “controlled localization environment”– Hides the complexity of localisation
Cisco Localization Toolkit Architecture
Cisco Localization Toolkit Workflow
Challenges of building a Toolkit
• It is a big task – needs to be well-defined to avoid scope creep• This has never been done before so there is no basis from
which to work, there is no reference material – just a problem to solve
• Designing a product-agnostic platform• Implementing the product-agnostic platform design (using a
lot of design patterns)• Fusing Java with the Common Object Model• Creating a variable codec generator
Challenges of using a Toolkit
• It costs money to do the localization• It is time consuming• The user has to have certain skills• There is a learning curve
Bottom Line: It is NOT a trivial task to localize a product, even WITH a localization toolkit
Toolkit Screenshots
Toolkit demo
What’s Next – Localization Toolkit 4.0
• Workflow component (TMS integration?)• Terminology Component (Multiterm
integration?)• Passolo Server with Cisco Toolkit front-
end• Usability improvements• Control-L(ocalize)???
Questions & Answers