Localization Roadmap Content Localization in DNN ne Xt

Sebastian Leupold Microsoft MVP dnn. Werk Verbund Deutschsprachige DNN-Usergroup DNN Localization Team German Translation

History and Current Situation � Content Localization added in DNN 5. 5 � Got

Requirements �Easy to translate (like editing content) �Professional Sites use External Translators • Central

Roadmap 1. 2. 3. 4. 5. 6. 7. 8. Support for Multilingual Modules “True”

I. Support for Multilingual Modules Module Type Support ML Content Localization Enable Default Allow

I. Support for Multilingual Modules � Using Flags in Module Definition • Supports multilingual

II. True Multilingual Pages /1 Page (Tab): �One Page (Same Tab. ID) for all

II. True Multilingual Pages /2 Modules: �Culture. Code in Page Link • • Extend

III. Translation Catalogue �Central Location for all Translations • Static • Semi-Dynamic Entities (Roles,

IV. Translation Interface �Interface for Modules & Core • Modules might use different data

V. Translate “in Situ” Detecting a piece of text on the page, where Translation

VI. Translation Center �for Admins and Onsite Translators �Lists all Texts • • ordered

VII. Export /Import Interface �Integrate external Translators �Ideal would be Push interface • No

VIII. Integration in Content Workflow must include Translation �Upon Content create �Upon Content update

Call for Action �Validation of Use Cases �Developers needed �Testers required �Documentation & Samples

Slides: 17

Download presentation

Localization Roadmap Content Localization in DNN ne. Xt Sebastian Leupold

Sebastian Leupold Microsoft MVP dnn. Werk Verbund Deutschsprachige DNN-Usergroup DNN Localization Team German Translation of DNN mailto: leupold@dnn. Werk. de

History and Current Situation � Content Localization added in DNN 5. 5 � Got Improved in DNN 5. 6, 6. 0 and 7. 1 � Limited Acceptance • Requires Following a Workflow • Complex Implementation � Bad Performance (### Pages*Languages) � Different Handling of Static and Content � No Support for Multilingual Modules � Missing Translation for Numerous Elements (Roles, …) Analysis of Stakeholders and Use Cases

Requirements �Easy to translate (like editing content) �Professional Sites use External Translators • Central UI • Export/Import �Translation Center with overview • What has been translated / needs to be translated �Avoid duplicate translations �Support for Multilingual Modules

Roadmap 1. 2. 3. 4. 5. 6. 7. 8. Support for Multilingual Modules “True” Multilingual Pages Central Translation Catalogue Translation Interface for Modules & Core Translate “in Situ” Translation Center Export/Import for external Translators Full Integration in Content Workflow

I. Support for Multilingual Modules Module Type Support ML Content Localization Enable Default Allow Localization Enable 1. No Localization available False 2. Localization possible, not suggested False True 3. Localization possible and suggested False True 4. Localization required, No ML support False True False 6. ML content supported, but optional True False True 7. ML content supported and suggested True 8. Always require ML content True False

I. Support for Multilingual Modules � Using Flags in Module Definition • Supports multilingual content • Content can be localized • Localization enabled by default � Option, when adding a Module to a Page • ML Content? (enable Translation UI) � Adding page Language: Instance/Referene � Interface for Translation Statistics � Module Names and Description localized

II. True Multilingual Pages /1 Page (Tab): �One Page (Same Tab. ID) for all languages • (currently: one Page per Language) �Tab. Localization Table • Tab. ID & Culture • Tab. Name �Multilingual Page Settings • Tab. Settings like Portal. Settings with Culture. Code • Neutral Fallback • Extensible for Skins and Modules

II. True Multilingual Pages /2 Modules: �Culture. Code in Page Link • • Extend PK of Tab. Modules Table by Culture Code ML Modules: one Record per Lang. same Module. ID Monolingual M: each record points to a diff. Module Null: display for all cultures �Display: Filtering Modules by Language �ML Module. Settings & Tab. Module. Settings • Null for Neutral/Fallback (like Portal. Settings)

III. Translation Catalogue �Central Location for all Translations • Static • Semi-Dynamic Entities (Roles, Lists, …) • Dynamic Content (versions) �Not necessarily storing Data, just Access �Dictionary attached �Infrastructure for the following Items

IV. Translation Interface �Interface for Modules & Core • Modules might use different data stores �Queried by the Translation Interface • Like DNN Search �Provides all Text to Translate �Provides Statistic Data

V. Translate “in Situ” Detecting a piece of text on the page, where Translation is missing/wrong Enter Edit Mode: Translate button appears on hover of each text Click it, Translate it System knows how to save it Required: Text key included (hidden) Modules need to support the interface

VI. Translation Center �for Admins and Onsite Translators �Lists all Texts • • ordered by Page & Tag ordered/filtered by Status Ordered by Author … �Provides text suggestions from dictionary or online translation center �For static text: Admin option: export to LP

VII. Export /Import Interface �Integrate external Translators �Ideal would be Push interface • No Standard available �Pull • • Interface (Translator request): X/Liff standard Preparation of text Export only missing translation / modified text Re-import translation and handover to source C.

VIII. Integration in Content Workflow must include Translation �Upon Content create �Upon Content update �Must be part of available WF Templates

Call for Action �Validation of Use Cases �Developers needed �Testers required �Documentation & Samples �Tutorials for Developers

Questions?