1. Multi-lingual
Implementations – Drupal
design approaches for
different scenarios

2. 1.
2.
Multilingual Concepts
3.
Multilingual
Design
Approaches
Why Multilingual ?
Drupal Multilingual Building blocks
4.
Scenarios
5.
Challenges
6.
Points to Consider
7.
Drupal Multilingual Roadmap
8.
Further Reading
9.
Q&A
2

3. 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
4

5. Multilingual Concepts

6.  i18n provides the ability to replace a
piece of content in one language by
its equivalent in another
Internationalization
 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.
6

7.  l10n is the actual process of creating
translated content
Localization
 Process of adapting a website for a
certain locale including :
 Translation of Text and Graphics
 Numeric, Date and Time formats
 Time Zones
7

8. Drupal Multilingual Building
Blocks

9. Multilingual
Translations
Elements
Content
Node Level
Users
Field Level
Menus
Building Blocks
Taxonomy
Blocks
Workflow
Interface
Content
Translation
9

10. 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
11

12. Scenarios
Which translation type to use ?

13.  An ecommerce website for a Retail
business needs to be built.
Scenario 1
 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.
13

14.  Products are same in all 3
languages
Scenario 1 –
Translation Type
 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
14

15.  Available in 2 languages - English
and French
 Per language revisions
Scenario 2
 Publication workflows - e.g.. the
French node can be in a prepublication 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
15

16.  2 nodes (English and French)
available for each page, thus
separate permissions can be
managed easily
Scenario 2 –
Translation Type
 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
16

17.  Available in 2 languages - Tamil and
Telugu
Scenario 3
 All the content needs to be translated
 Comments should not be intermixed
 Polls and events are common to both
the languages
17

18.  Both content translation types will be
used
Scenario 3 –
Translation Type
 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
18

19.  Different UI for Entity Translation/
Content Translation is confusing
Challenges
 Professional Translators need to
learn Drupal
 Need to build system for reviewing
translation
19

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 ?
20

21. Where Drupal 8
is headed with
Multilingual ?
21

22.  Multilingual Guide
https://drupal.org/documentation/mult
ilingual
Further Reading
 Translating Interface
https://drupal.org/documentation/mo
dules/locale
 http://www.drupal8multilingual.org/
22

23. Q&A
© 2013 SAPIENT CORPORATION | CONFIDENTIAL