Multi-lingual Implementations – Drupal design approaches for different scenarios

2

Multilingual Design Approaches

1. Why Multilingual ?

2. Multilingual Concepts

3. Drupal Multilingual Building blocks

4. Scenarios

5. Challenges

6. Points to Consider

7. Drupal Multilingual Roadmap

8. Further Reading

9. Q & A

Why Multilingual ?

4

Business needs to build a Multilingual site

To Reach a wider audience

To Increase Site Traffic and Sales

To Expand to new markets

To Improve usability

Multilingual Concepts

6

Internationalization

i18n provides the ability to replace a piece of content in one language by its equivalent in another

Developing a website that enables localization of content and other elements

If you have an “about me” page in English, i18n will enable you to create versions of it in other languages and have them displayed to visitors depending on their selected locale.

7

Localization

l10n is the actual process of creating translated content

Process of adapting a website for a certain locale including :

Translation of Text and Graphics

Numeric, Date and Time formats

Time Zones

Drupal Multilingual Building Blocks

9

Building Blocks

MultilingualTranslations

Content

Node Level

Field Level

Elements

Users

Menus

Taxonomy

Blocks

Workflow

Content

Translation

Interface

Building blocks deep dive

Other Translation Building block sections – Elements, Interface, Workflow are WIP

11

Node Level Translation - one node per translation

Field Level Translation - one node with many translation

ScenariosWhich translation type to use ?

13

Scenario 1

An ecommerce website for a Retail business needs to be built.

This website will be accessible in 3 languages (Hindi, Punjabi and Gujarati).

All the content, products needs to be translated.

Users will be able to browse and buy products.

14

Scenario 1 – Translation Type

Products are same in all 3 languages

Symmetric Behavior – Menus, Taxonomy, nodes are same

Purchase product from Punjabi website, reflect available quantity in rest of the sites.

Use Entity Translation for a scenario where a product is involved in transactions

15

Scenario 2

Available in 2 languages - English and French

Per language revisions

Publication workflows - e.g.. the French node can be in a pre-publication revision workflow while the English is already published

Permission handling - e.g.. certain people can only edit French translations not English originals

Content might be different from each other in both the languages

16

Scenario 2 – Translation Type

2 nodes (English and French) available for each page, thus separate permissions can be managed easily

Roles "French Editor" and "English Editor" can be created

Edit permissions can be set for these editors based on their language and thus they can manage the workflow independently

Revisions can be maintained for both the languages

Use Node Translation

17

Scenario 3

Available in 2 languages - Tamil and Telugu

All the content needs to be translated

Comments should not be intermixed

Polls and events are common to both the languages

18

Scenario 3 – Translation Type

Both content translation types will be used

Node Translation allows to create separate nodes and thus commenting will not be intermixed

Entity Translation will be used for Events and Polls

There will be one node to combine poll results of both English and French users

19

Challenges

Different UI for Entity Translation/ Content Translation is confusing

Professional Translators need to learn Drupal

Need to build system for reviewing translation

20

Points to consider

How many languages you need to support ?

Does the user interface need to be fully translated

Do you have content in all the languages ? Is all the content translated ?

21

Where Drupal 8 is headed with Multilingual ?

22

Further Reading

Multilingual Guide https://drupal.org/documentation/multilingual

Translating Interface https://drupal.org/documentation/modules/locale

http://www.drupal8multilingual.org/

© 2013 SAPIENT CORPORATION | CONFIDENTIAL

Q & A