EVOLVE'13 | Enhance | Localization | Keith Brazil

615 views
503 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
615
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

EVOLVE'13 | Enhance | Localization | Keith Brazil

  1. 1. Your Global Content – What is Below the Surface • Client Name
  2. 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. 3. Globalization in Adobe Experience Manager (AEM)
  4. 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. 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. 6. What’s missing? • Linguistic technologies • Translation memory • Machine translation • Language review portal • Terminology and style constraints • Reporting and quoting • Vendor management
  7. 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. 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. 9. More on components • Granular control of translatable components • Exhaustive list • Wildcards with exclusion list support • Translatability patterns
  10. 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. 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?
  12. 12. GlobalLink AEM Adaptor
  13. 13. 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
  14. 14. Thank You! QUESTIONS?
  15. 15. 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

×