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