This document contrasts the multilingual support in Drupal 7 and Drupal 8. It discusses how in Drupal 7 multilingual capabilities were an afterthought added through contributed modules, while in Drupal 8 multilingual functionality was a core consideration from the beginning. The document then demonstrates preparing a Drupal 8 website for multilingual support, showing both the traditional translation process within Drupal 8 itself as well as using Lingotek translation management.

1. Josh Solomon, Product Manager, Lingotek
Gábor Hojtsy, Drupal Core Developer, Acquia
Drupal 7 vs. Drupal 8: A Contrast
of Multilingual Support

2. Lingotek – Company Overview

4. Drupal 7 vs Drupal 8 - A Contrast of Multilingual Support
1. Review the Drupal 7 multilingual landscape in contrast to Drupal 8’s core
multilingual capabilities.
2. Demonstrate how to properly prepare a Drupal 8 website for multilingual
support
3. Show the traditional process of translating Drupal 8 websites
4. Explore the Lingotek translation process for Drupal 8 websites
Objectives

5. Afterthought vs Forethought
Multilingual Drupal 7 vs Drupal 8

6. Drupal 7 – Multilingual Afterthought…

7. Drupal 8 – Multilingual Forethought…
LANGUAGE INTERFACE CONTENT CONFIG

8. Drupal 8: Language
–Base services for all
modules dealing with data.
–Not just multilingual

9. Drupal 8: Interface
–Interface translation has
a built-in update feature
and improves usability.

10. Drupal 8: Content
–Field translation in a
built-in API for all entities.
–Content translation
provides user interface.

11. Drupal 8: Configuration
–Common configuration
system handles blocks,
views, field settings.
–Unified translation

12. 1. Not strictly needed to think of language at the
start
2. Contributed modules took time to adapt
3. Migration path improved but still has some holes
Preparing Drupal 8 for Multilingual

13. 1. Built-in D8 translation process
2. D8 + Lingotek Translation process
Demo: Translating Drupal 8

14. Thank You