EVOLVE'13 | Enhance | Localization | Keith Brazil
•Download as PPTX, PDF•
1 like•797 views
Recommended
Recommended
More Related Content
What's hot
Viewers also liked
Viewers also liked (20)
Similar to EVOLVE'13 | Enhance | Localization | Keith Brazil
Similar to EVOLVE'13 | Enhance | Localization | Keith Brazil (20)
More from Evolve The Adobe Digital Marketing Community
More from Evolve The Adobe Digital Marketing Community (20)
Recently uploaded
Recently uploaded (20)
EVOLVE'13 | Enhance | Localization | Keith Brazil
- 1. Your Global Content – What is Below the Surface • Client Name
- 2. COMPANY PROFILE • Founded 1992 • 80+ Offices Worldwide • 20,000+ Clients • 2,100+ Employees • 22 Global Production Centers • GlobalLink® Suite • Mature Adobe CQ Integration
- 3. Globalization in Adobe Experience Manager (AEM)
- 4. AEM and Globalization • AEM is already very well equipped for translation • Multilingual Site Manager (MSM) • Componentized XML • Strong integration points • Easy to use workflow modeler
- 5. What’s missing? • Translation automation and management • Identification and extraction of translatable components from within AEM • Transmission to a translation workflow service • Pull back and reintegration of translations
- 6. What’s missing? • Linguistic technologies • Translation memory • Machine translation • Language review portal • Terminology and style constraints • Reporting and quoting • Vendor management
- 7. Getting it all started • Who decides what needs translation and how? • Ad hoc requirement never goes away • Bulk mode for new languages • Emergency submissions • Translation as part of the authoring workflow • Automation of maintenance mode
- 8. More factors to consider • What are my translatable components? • What / Who determines translatability? • Pseudo-translation dye testing • AEM Multi Site Manager? • No brainer right? • What about Live Copy?
- 9. More on components • Granular control of translatable components • Exhaustive list • Wildcards with exclusion list support • Translatability patterns
- 10. Even more factors to consider • Aside from components, what else needs translation? • DAM Assets? • Application resource bundles? • Other external assets? • Tags • Reference components
- 11. More factors to consider • What to do with delivered translated content? • Trigger workflows? • Who needs to review in AEM? • How to capture changes to translated content made within AEM?
- 14. Best Practices • Best practices • Use MSM • Indicate translatability in component names • Limit “hot fix” language changes in AEM • Allow markets their own local components • Get local market buy in early, and often
- 16. Thank You! Keith Brazil VP, Technology +1 212 689 1616 kbrazil@translations.com Nick Panagopoulos Director, Strategic Alliances +1 312 236 1606 npanagopoulos@translations.com