CMS and localisation Multilingual Web content management Limerick. - PowerPoint PPT Presentation

Multilingual Web Conference CMS and localisation Multilingual Web content management Limerick. September 21st, 2011 Page 1

ID Cocomore essentials Agency for integrated communication and IT services 100 employees Offices in Germany and Bulgaria Our clients include Fresenius, Nestlé, Procter & Gamble, PwC, RTL, Sanofi-Aventis Drupal is our CMS of choice Page 2

Cocomore and Drupal Health portal ellviva.de Features: • Built on Drupal with additional functionalities • >100,000 pages of content • Linked to legacy systems, for example pharmaceutical information systems • Editorial backend including complex workflows and image database Page 3

Cocomore and Drupal Implemented multilingualism capabilities • Clustering of content nodes across languages: Content node cluster - Source language node - Target language 1 node - Target language 2 node Target language … node - Content node links across languages Page 4

Cocomore and Drupal Implemented multilingualism capabilities • Editorial backend workflows for translations • Apache Solr Multilingual • Multilingual search • Stop-word parsing • Stemming parsing • Compound noun parsing • … Page 5

Multilingualism on the Web Demand for multilingual content Client demands More clients want to serve an increasing number of relevant language markets Multilingual Web content Content viewers can be from various language backgrounds CMS requirements CMS must be able to provide multilingual content and integrate necessary functionalities This often means being able to integrate translated content into the CMS Page 6

Multilingual CMS issues Terms and terminology Fixed terms and terminology are accidentally translated: Unser Berater John (…) Our consultant John will help you Page 7

Multilingual CMS issues Terms and terminology Metadata marking of terms can avoid the problem: Unser Berater John (…) Our consultant John will help you Unser Consultant John (…) !TERM! Possible terms Brands Product names Academic terminologies Technical terminologies … Page 8

Multilingual CMS issues Terms and terminology Metadata marking of terms can avoid the problem: Business rules are important Geschäftsregeln sind wichtig !TERM! Business Rules sind wichtig Page 9

Multilingual CMS issues Terms and terminology Metadata marking of terms can avoid the problem: We know alle touch points Wir kennen alle Berührungspunkte !TERM! Wir kennen alle Touch Points Page 10

Multilingual CMS issues Terms and terminology Non-translatability of terminology can be language-specific: Our consultant John will help you Unser Consultant John (…) !TERM! (…) コンサルタント (…) Page 11

Multilingual CMS issues Domains Lack of domain information can create MT translation issues: Der Ursprung des Willens (…) The origins of sake are unclear Page 12

Multilingual CMS issues Domains Lack of domain information can create MT translation issues: Der Ursprung des Willens (…) The origins of sake are unclear Der Ursprung von Sake (…) !DOMAIN! Content domains (legal, medical , …) Possible domains Audience domains (formal/informal, academic , …) Page 13

Multilingual CMS issues Domains Translations should differ depending on the audience: Could you pass the butter? Könntest du mir die Butter reichen? Page 14

Multilingual CMS issues Domains Translations should differ depending on the audience: Could you pass the butter? Könntest du mir die Butter reichen? Könnten Sie mir (…)? !DOMAIN! Könntet ihr mir (…)? Page 15

Multilingual CMS issues Translation workflow integration Currently, translations are often dealt with like this: Content Exported content Translation import Content includes Re-introduction of Loss of formatting, formatting, formatting, re- embedded content, embedded content, embedding of … … content , … Page 16

Multilingual CMS issues Translation workflow integration This is what we would like the process to be: Encapsulation (using e.g. XLIFF) Content node cluster Content meta information relevant to Transfer to LSP Source language CMS (storage information , … ) Target language Domain metadata Content with intra- content metadata Integration of Encapsulated Decapsulation translated content translation Page 17

How to tackle these issues Cooperation of LSP and CMS CMS Solution LSP CMS view of Integration of expertise multilingual issues and needs of both sides, so that We need: • Metadata standard • CMS can provide • Agreed-on content multilingual content formats (e.g. XLIFF) LSP view of multilingual management to issues clients We can: • Integrate metadata • LSP can improve into workflows accuracy, speed and • Develop cost-efficiency of encapsulation / their services export modules Page 18

How to tackle these issues MultilingualWeb-LT as big leap forward MultilingualWeb-LT Aligns both LSP and CMS Will create metadata standard to improve translations Cocomore will implement metadata standard into Drupal (CMS) content workflows LSP can improve quality of translations with the help of metadata Page 19

The bottom line Benefits for clients MultilingualWeb-LT Better ways of dealing with translations in the CMS Improved quality of translations, impact on translation costs and efficiency Increased ability to provide multilingual content to tackle new opportunites and thrive in new markets Page 20

Thank you for your time. Page 21