evolve'13 | enhance | localization | keith brazil

Post on 27-Nov-2014

537 Views

Category:

Technology

4 Downloads

Preview:

Click to see full reader

DESCRIPTION

 

TRANSCRIPT

Your Global Content – What is Below the Surface

• Client Name

COMPANY PROFILE

• Founded 1992• 80+ Offices Worldwide• 20,000+ Clients• 2,100+ Employees• 22 Global Production Centers• GlobalLink® Suite• Mature Adobe CQ Integration

Globalization in Adobe Experience Manager (AEM)

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

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

What’s missing?

• Linguistic technologies• Translation memory• Machine translation• Language review portal• Terminology and style constraints• Reporting and quoting• Vendor management

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

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?

More on components

• Granular control of translatable components• Exhaustive list• Wildcards with exclusion list support• Translatability patterns

Even more factors to consider

• Aside from components, what else needs translation?• DAM Assets?• Application resource bundles?• Other external assets?• Tags• Reference components

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?

GlobalLink AEM Adaptor

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

Thank You!

QUESTIONS?

Thank You!

Keith BrazilVP, Technology+1 212 689 1616kbrazil@translations.com

Nick PanagopoulosDirector, Strategic Alliances+1 312 236 1606npanagopoulos@translations.com

top related